Drag motion across seam of displays

ABSTRACT

Methods and devices for receiving input and presenting a user interface with two screens and an off screen gesture area. The device may have an off screen gesture area that accepts user input outside the display area. The interface inputs received in the off screen gesture are may have special handling and cause different display changes. Further, the device, having two screens, may receive user interface inputs that cross the seam between the two displays. To provide a display that acts like a single display area, the device can predict motions may cross the seam and then interrelate separate inputs on separate screens. The interrelated inputs can cause display changes as if the inputs were received as a single user interaction.

CROSS REFERENCE TO RELATED APPLICATION

The present application claims the benefits of and priority, under 35U.S.C. §119(e), to U.S. Provisional Application Ser. No. 61/539,884,filed Sep. 27, 2011, entitled “MOBILE DEVICE,” and this application isincorporated herein by reference in its entirety for all that it teachesand for all purposes.

BACKGROUND

A substantial number of handheld computing devices, such as cellularphones, tablets, and E-Readers, make use of a touch screen display notonly to deliver display information to the user but also to receiveinputs from user interface commands. While touch screen displays mayincrease the configurability of the handheld device and provide a widevariety of user interface options, this flexibility typically comes at aprice. The dual use of the touch screen to provide content and receiveuser commands, while flexible for the user, may obfuscate the displayand cause visual clutter, thereby leading to user frustration and lossof productivity.

The small form factor of handheld computing devices requires a carefulbalancing between the displayed graphics and the area provided forreceiving inputs. On the one hand, the small display constrains thedisplay space, which may increase the difficulty of interpreting actionsor results. On the other, a virtual keypad or other user interfacescheme is superimposed on or positioned adjacent to an executingapplication, requiring the application to be squeezed into an evensmaller portion of the display.

This balancing act is particularly difficult for single display touchscreen devices. Single display touch screen devices are crippled bytheir limited screen space. When users are entering information into thedevice, through the single display, the ability to interpret informationin the display can be severely hampered, particularly when a complexinteraction between display and interface is required.

SUMMARY

There is a need for a dual multi-display handheld computing device thatprovides for enhanced power and/or versatility compared to conventionalsingle display handheld computing devices. These and other needs areaddressed by the various aspects, embodiments, and/or configurations ofthe present disclosure. Also, while the disclosure is presented in termsof exemplary embodiments, it should be appreciated that individualaspects of the disclosure can be separately claimed.

Additionally, it is desirable to have the multi-display device that canuse either display when the device is closed. Thus, the user, based onthe user's desires, can take better advantage of the phonescapabilities. The device can have at least two screens that face inopposite directions when closed. A primary screen may be used for mostapplications. However, the user, or by some other input or event, canchange the display to a secondary screen. Thus, the display may beprovided on the opposite screen facing the opposite direction.

The device can include special user interaction features. For example,the device may have an off screen gesture area that accepts user inputoutside the display area. The interface inputs received in the offscreen gesture are may have special handling and cause different displaychanges. Further, the device, having two screens, may receive userinterface inputs that cross the seam between the two displays. Toprovide a display that acts like a single display area, the device canpredict motions may cross the seam and then interrelate separate inputson separate screens. The interrelated inputs can cause display changesas if the inputs were received as a single user interaction.

The phrases “at least one”, “one or more”, and “and/or” are open-endedexpressions that are both conjunctive and disjunctive in operation. Forexample, each of the expressions “at least one of A, B and C”, “at leastone of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B,or C” and “A, B, and/or C” means A alone, B alone, C alone, A and Btogether, A and C together, B and C together, or A, B and C together.

The term “a” or “an” entity refers to one or more of that entity. Assuch, the terms “a” (or “an”), “one or more” and “at least one” can beused interchangeably herein. It is also to be noted that the terms“comprising”, “including”, and “having” can be used interchangeably.

The term “automatic” and variations thereof, as used herein, refers toany process or operation done without material human input when theprocess or operation is performed. However, a process or operation canbe automatic, even though performance of the process or operation usesmaterial or immaterial human input, if the input is received beforeperformance of the process or operation. Human input is deemed to bematerial if such input influences how the process or operation will beperformed. Human input that consents to the performance of the processor operation is not deemed to be “material”.

The term “computer-readable medium” as used herein refers to anytangible storage and/or transmission medium that participate inproviding instructions to a processor for execution. Such a medium maytake many forms, including but not limited to, non-volatile media,volatile media, and transmission media. Non-volatile media includes, forexample, NVRAM, or magnetic or optical disks. Volatile media includesdynamic memory, such as main memory. Common forms of computer-readablemedia include, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, or any other magnetic medium, magneto-optical medium, aCD-ROM, any other optical medium, punch cards, paper tape, any otherphysical medium with patterns of holes, a RAM, a PROM, and EPROM, aFLASH-EPROM, a solid state medium like a memory card, any other memorychip or cartridge, a carrier wave as described hereinafter, or any othermedium from which a computer can read. A digital file attachment toe-mail or other self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. When the computer-readable media is configured as a database, itis to be understood that the database may be any type of database, suchas relational, hierarchical, object-oriented, and/or the like.Accordingly, the disclosure is considered to include a tangible storagemedium or distribution medium and prior art-recognized equivalents andsuccessor media, in which the software implementations of the presentdisclosure are stored.

The term “desktop” refers to a metaphor used to portray systems. Adesktop is generally considered a “surface” that typically includespictures, called icons, widgets, folders, etc. that can activate showapplications, windows, cabinets, files, folders, documents, and othergraphical items. The icons are generally selectable to initiate a taskthrough user interface interaction to allow a user to executeapplications or conduct other operations.

The term “screen,” “touch screen,” or “touchscreen” refers to a physicalstructure that includes one or more hardware components that provide thedevice with the ability to render a user interface and/or receive userinput. A screen can encompass any combination of gesture capture region,a touch sensitive display, and/or a configurable area. The device canhave one or more physical screens embedded in the hardware. However ascreen may also include an external peripheral device that may beattached and detached from the device. In embodiments, multiple externaldevices may be attached to the device. Thus, in embodiments, the screencan enable the user to interact with the device by touching areas on thescreen and provides information to a user through a display. The touchscreen may sense user contact in a number of different ways, such as bya change in an electrical parameter (e.g., resistance or capacitance),acoustic wave variations, infrared radiation proximity detection, lightvariation detection, and the like. In a resistive touch screen, forexample, normally separated conductive and resistive metallic layers inthe screen pass an electrical current. When a user touches the screen,the two layers make contact in the contacted location, whereby a changein electrical field is noted and the coordinates of the contactedlocation calculated. In a capacitive touch screen, a capacitive layerstores electrical charge, which is discharged to the user upon contactwith the touch screen, causing a decrease in the charge of thecapacitive layer. The decrease is measured, and the contacted locationcoordinates determined. In a surface acoustic wave touch screen, anacoustic wave is transmitted through the screen, and the acoustic waveis disturbed by user contact. A receiving transducer detects the usercontact instance and determines the contacted location coordinates.

The term “display” refers to a portion of one or more screens used todisplay the output of a computer to a user. A display may be asingle-screen display or a multi-screen display, referred to as acomposite display. A composite display can encompass the touch sensitivedisplay of one or more screens. A single physical screen can includemultiple displays that are managed as separate logical displays. Thus,different content can be displayed on the separate displays althoughpart of the same physical screen.

The term “displayed image” refers to an image produced on the display. Atypical displayed image is a window or desktop. The displayed image mayoccupy all or a portion of the display.

The term “display orientation” refers to the way in which a rectangulardisplay is oriented by a user for viewing. The two most common types ofdisplay orientation are portrait and landscape. In landscape mode, thedisplay is oriented such that the width of the display is greater thanthe height of the display (such as a 4:3 ratio, which is 4 units wideand 3 units tall, or a 16:9 ratio, which is 16 units wide and 9 unitstall). Stated differently, the longer dimension of the display isoriented substantially horizontal in landscape mode while the shorterdimension of the display is oriented substantially vertical. In theportrait mode, by contrast, the display is oriented such that the widthof the display is less than the height of the display. Stateddifferently, the shorter dimension of the display is orientedsubstantially horizontal in the portrait mode while the longer dimensionof the display is oriented substantially vertical.

The term “composite display” refers to a logical structure that definesa display that can encompass one or more screens. A multi-screen displaycan be associated with a composite display that encompasses all thescreens. The composite display can have different displaycharacteristics based on the various orientations of the device.

The term “gesture” refers to a user action that expresses an intendedidea, action, meaning, result, and/or outcome. The user action caninclude manipulating a device (e.g., opening or closing a device,changing a device orientation, moving a trackball or wheel, etc.),movement of a body part in relation to the device, movement of animplement or tool in relation to the device, audio inputs, etc. Agesture may be made on a device (such as on the screen) or with thedevice to interact with the device.

The term “module” as used herein refers to any known or later developedhardware, software, firmware, artificial intelligence, fuzzy logic, orcombination of hardware and software that is capable of performing thefunctionality associated with that element.

The term “gesture capture” refers to a sense or otherwise a detection ofan instance and/or type of user gesture. The gesture capture can occurin one or more areas of the screen, A gesture region can be on thedisplay, where it may be referred to as a touch sensitive display or offthe display where it may be referred to as a gesture capture area.

A “multi-screen application” or “multiple-display application” refers toan application that is capable of multiple modes. The multi-screenapplication mode can include, but is not limited to, a single screenmode (where the application is displayed on a single screen) or acomposite display mode (where the application is displayed on two ormore screens). A multi-screen application can have different layoutsoptimized for the mode. Thus, the multi-screen application can havedifferent layouts for a single screen or for a composite display thatcan encompass two or more screens. The different layouts may havedifferent screen/display dimensions and/or configurations on which theuser interfaces of the multi-screen applications can be rendered. Thedifferent layouts allow the application to optimize the application'suser interface for the type of display, e.g., single screen or multiplescreens. In single screen mode, the multi-screen application may presentone window pane of information. In a composite display mode, themulti-screen application may present multiple window panes ofinformation or may provide a larger and a richer presentation becausethere is more space for the display contents. The multi-screenapplications may be designed to adapt dynamically to changes in thedevice and the mode depending on which display (single or composite) thesystem assigns to the multi-screen application. In alternativeembodiments, the user can use a gesture to request the applicationtransition to a different mode, and, if a display is available for therequested mode, the device can allow the application to move to thatdisplay and transition modes.

A “single-screen application” refers to an application that is capableof single screen mode. Thus, the single-screen application can produceonly one window and may not be capable of different modes or differentdisplay dimensions. A single-screen application may not be capable ofthe several modes discussed with the multi-screen application.

The term “window” refers to a, typically rectangular, displayed image onat least part of a display that contains or provides content differentfrom the rest of the screen. The window may obscure the desktop.

The terms “determine”, “calculate” and “compute,” and variationsthereof, as used herein, are used interchangeably and include any typeof methodology, process, mathematical operation or technique.

It shall be understood that the term “means” as used herein shall begiven its broadest possible interpretation in accordance with 35 U.S.C.,Section 112, Paragraph 6. Accordingly, a claim incorporating the term“means” shall cover all structures, materials, or acts set forth herein,and all of the equivalents thereof. Further, the structures, materialsor acts and the equivalents thereof shall include all those described inthe summary of the invention, brief description of the drawings,detailed description, abstract, and claims themselves.

The preceding is a simplified summary of the disclosure to provide anunderstanding of some aspects of the disclosure. This summary is neitheran extensive nor exhaustive overview of the disclosure and its variousaspects, embodiments, and/or configurations. It is intended neither toidentify key or critical elements of the disclosure nor to delineate thescope of the disclosure but to present selected concepts of thedisclosure in a simplified form as an introduction to the more detaileddescription presented below. As will be appreciated, other aspects,embodiments, and/or configurations of the disclosure are possibleutilizing, alone or in combination, one or more of the features setforth above or described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A includes a first view of an embodiment of a multi-screen userdevice;

FIG. 1B includes a second view of an embodiment of a multi-screen userdevice;

FIG. 1C includes a third view of an embodiment of a multi-screen userdevice;

FIG. 1D includes a fourth view of an embodiment of a multi-screen userdevice;

FIG. 1E includes a fifth view of an embodiment of a multi-screen userdevice;

FIG. 1F includes a sixth view of an embodiment of a multi-screen userdevice;

FIG. 1G includes a seventh view of an embodiment of a multi-screen userdevice;

FIG. 1H includes a eighth view of an embodiment of a multi-screen userdevice;

FIG. 1I includes a ninth view of an embodiment of a multi-screen userdevice;

FIG. 1J includes a tenth view of an embodiment of a multi-screen userdevice;

FIG. 2 is a block diagram of an embodiment of the hardware of thedevice;

FIG. 3A is a block diagram of an embodiment of the state model for thedevice based on the device's orientation and/or configuration;

FIG. 3B is a table of an embodiment of the state model for the devicebased on the device's orientation and/or configuration;

FIG. 4A is a first representation of an embodiment of user gesturereceived at a device;

FIG. 4B is a second representation of an embodiment of user gesturereceived at a device;

FIG. 4C is a third representation of an embodiment of user gesturereceived at a device;

FIG. 4D is a fourth representation of an embodiment of user gesturereceived at a device;

FIG. 4E is a fifth representation of an embodiment of user gesturereceived at a device;

FIG. 4F is a sixth representation of an embodiment of user gesturereceived at a device;

FIG. 4G is a seventh representation of an embodiment of user gesturereceived at a device;

FIG. 4H is a eighth representation of an embodiment of user gesturereceived at a device;

FIG. 5A is a block diagram of an embodiment of the device softwareand/or firmware;

FIG. 5B is a second block diagram of an embodiment of the devicesoftware and/or firmware;

FIG. 6A is a first representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6B is a second representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6C is a third representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6D is a fourth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6E is a fifth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6F is a sixth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6G is a seventh representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6H is a eighth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6I is a ninth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6J is a tenth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 7A is representation of a logical window stack;

FIG. 7B is another representation of an embodiment of a logical windowstack;

FIG. 7C is another representation of an embodiment of a logical windowstack;

FIG. 7D is another representation of an embodiment of a logical windowstack;

FIG. 7E is another representation of an embodiment of a logical windowstack;

FIG. 8 is block diagram of an embodiment of a logical data structure fora window stack;

FIG. 9 is a flow chart of an embodiment of a method for creating awindow stack;

FIG. 10 illustrates an exemplary method for managing the display of anemail client application based on application mode and deviceconfiguration;

FIG. 11 is a flow diagram of an embodiment of a method for receivinginput into the device;

FIG. 12 illustrates an exemplary user interface interaction forreceiving input into the device;

FIG. 13 illustrates another exemplary user interface interaction forreceiving input into the device;

FIG. 14 illustrates another exemplary user interface interaction forreceiving input into the device;

FIG. 15 is a flow diagram of an embodiment of a method for receivinginput into the device;

FIG. 16 illustrates another exemplary user interface interaction forreceiving input into the device;

FIG. 17 illustrates another exemplary user interface interaction forreceiving input into the device;

FIG. 18 illustrates another exemplary user interface interaction forreceiving input into the device;

FIG. 19 is another flow diagram of an embodiment of a method forreceiving input into the device.

In the appended figures, similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a letter thatdistinguishes among the similar components. If only the first referencelabel is used in the specification, the description is applicable to anyone of the similar components having the same first reference labelirrespective of the second reference label.

DETAILED DESCRIPTION

Presented herein are embodiments of a device. The device can be acommunications device, such as a cellular telephone, or other smartdevice. The device can include two screens that are oriented to provideseveral unique display configurations. Further, the device can receiveuser input in unique ways. The overall design and functionality of thedevice provides for an enhanced user experience making the device moreuseful and more efficient.

Mechanical Features:

FIGS. 1A-1J illustrate a device 100 in accordance with embodiments ofthe present disclosure. As described in greater detail below, device 100can be positioned in a number of different ways each of which providesdifferent functionality to a user. The device 100 is a multi-screendevice that includes a primary screen 104 and a secondary screen 108,both of which are touch sensitive. In embodiments, the entire frontsurface of screens 104 and 108 may be touch sensitive and capable ofreceiving input by a user touching the front surface of the screens 104and 108. Primary screen 104 includes touch sensitive display 110, which,in addition to being touch sensitive, also displays information to auser. Secondary screen 108 includes touch sensitive display 114, whichalso displays information to a user. In other embodiments, screens 104and 108 may include more than one display area.

Primary screen 104 also includes a configurable area 112 that has beenconfigured for specific inputs when the user touches portions of theconfigurable area 112. Secondary screen 108 also includes a configurablearea 116 that has been configured for specific inputs. Areas 112 a and116 a have been configured to receive a “back” input indicating that auser would like to view information previously displayed. Areas 112 band 116 b have been configured to receive a “menu” input indicating thatthe user would like to view options from a menu. Areas 112 c and 116 chave been configured to receive a “home” input indicating that the userwould like to view information associated with a “home” view. In otherembodiments, areas 112 a-c and 116 a-c may be configured, in addition tothe configurations described above, for other types of specific inputsincluding controlling features of device 100, some non-limiting examplesincluding adjusting overall system power, adjusting the volume,adjusting the brightness, adjusting the vibration, selecting ofdisplayed items (on either of screen 104 or 108), operating a camera,operating a microphone, and initiating/terminating of telephone calls.Also, in some embodiments, areas 112 a-C and 116 a-C may be configuredfor specific inputs depending upon the application running on device 100and/or information displayed on touch sensitive displays 110 and/or 114.

In addition to touch sensing, primary screen 104 and secondary screen108 may also include areas that receive input from a user withoutrequiring the user to touch the display area of the screen. For example,primary screen 104 includes gesture capture area 120, and secondaryscreen 108 includes gesture capture area 124. These areas are able toreceive input by recognizing gestures made by a user without the needfor the user to actually touch the surface of the display area. Incomparison to touch sensitive displays 110 and 114, the gesture captureareas 120 and 124 are commonly not capable of rendering a displayedimage.

The two screens 104 and 108 are connected together with a hinge 128,shown clearly in FIG. 1C (illustrating a back view of device 100). Hinge128, in the embodiment shown in FIGS. 1A-1J, is a center hinge thatconnects screens 104 and 108 so that when the hinge is closed, screens104 and 108 are juxtaposed (i.e., side-by-side) as shown in FIG. 1B(illustrating a front view of device 100). Hinge 128 can be opened toposition the two screens 104 and 108 in different relative positions toeach other. As described in greater detail below, the device 100 mayhave different functionalities depending on the relative positions ofscreens 104 and 108.

FIG. 1D illustrates the right side of device 100. As shown in FIG. 1D,secondary screen 108 also includes a card slot 132 and a port 136 on itsside. Card slot 132 in embodiments, accommodates different types ofcards including a subscriber identity module (SIM). Port 136 inembodiments is an input/output port (I/O port) that allows device 100 tobe connected to other peripheral devices, such as a display, keyboard,or printing device. As can be appreciated, these are merely someexamples and in other embodiments device 100 may include other slots andports such as slots and ports for accommodating additional memorydevices and/or for connecting other peripheral devices. Also shown inFIG. 1D is an audio jack 140 that accommodates a tip, ring, sleeve (TRS)connector for example to allow a user to utilize headphones or aheadset.

Device 100 also includes a number of buttons 158. For example, FIG. 1Eillustrates the left side of device 100. As shown in FIG. 1E, the sideof primary screen 104 includes three buttons 144, 148, and 152, whichcan be configured for specific inputs. For example, buttons 144, 148,and 152 may be configured to, in combination or alone, control a numberof aspects of device 100. Some non-limiting examples include overallsystem power, volume, brightness, vibration, selection of displayeditems (on either of screen 104 or 108), a camera, a microphone, andinitiation/termination of telephone calls. In some embodiments, insteadof separate buttons two buttons may be combined into a rocker button.This arrangement is useful in situations where the buttons areconfigured to control features such as volume or brightness. In additionto buttons 144, 148, and 152, device 100 also includes a button 156,shown in FIG. 1F, which illustrates the top of device 100. In oneembodiment, button 156 is configured as an on/off button used to controloverall system power to device 100. In other embodiments, button 156 isconfigured to, in addition to or in lieu of controlling system power,control other aspects of device 100. In some embodiments, one or more ofthe buttons 144, 148, 152, and 156 are capable of supporting differentuser commands. By way of example, a normal press has a duration commonlyof less than about 1 second and resembles a quick tap. A medium presshas a duration commonly of 1 second or more but less than about 12seconds. A long press has a duration commonly of about 12 seconds ormore. The function of the buttons is normally specific to theapplication that is currently in focus on the respective display 110 and114. In a telephone application for instance and depending on theparticular button, a normal, medium, or long press can mean end call,increase in call volume, decrease in call volume, and toggle microphonemute. In a camera or video application for instance and depending on theparticular button, a normal, medium, or long press can mean increasezoom, decrease zoom, and take photograph or record video.

There are also a number of hardware components within device 100. Asillustrated in FIG. 1C, device 100 includes a speaker 160 and amicrophone 164. Device 100 also includes a camera 168 (FIG. 1B).Additionally, device 100 includes two position sensors 172A and 172B,which are used to determine the relative positions of screens 104 and108. In one embodiment, position sensors 172A and 172B are Hall effectsensors. However, in other embodiments other sensors can be used inaddition to or in lieu of the Hall effect sensors. An accelerometer 176may also be included as part of device 100 to determine the orientationof the device 100 and/or the orientation of screens 104 and 108.Additional internal hardware components that may be included in device100 are described below with respect to FIG. 2.

The overall design of device 100 allows it to provide additionalfunctionality not available in other communication devices. Some of thefunctionality is based on the various positions and orientations thatdevice 100 can have. As shown in FIGS. 1B-1G, device 100 can be operatedin an “open” position where screens 104 and 108 are juxtaposed. Thisposition allows a large display area for displaying information to auser. When position sensors 172A and 172B determine that device 100 isin the open position, they can generate a signal that can be used totrigger different events such as displaying information on both screens104 and 108. Additional events may be triggered if accelerometer 176determines that device 100 is in a portrait position (FIG. 1B) asopposed to a landscape position (not shown).

In addition to the open position, device 100 may also have a “closed”position illustrated in FIG. 1H. Again, position sensors 172A and 172Bcan generate a signal indicating that device 100 is in the “closed”position. This can trigger an event that results in a change ofdisplayed information on screen 104 and/or 108. For example, device 100may be programmed to stop displaying information on one of the screens,e.g., screen 108, since a user can only view one screen at a time whendevice 100 is in the “closed” position. In other embodiments, the signalgenerated by position sensors 172A and 172B, indicating that the device100 is in the “closed” position, can trigger device 100 to answer anincoming telephone call. The “closed” position can also be a preferredposition for utilizing the device 100 as a mobile phone.

Device 100 can also be used in an “easel” position which is illustratedin FIG. 1I. In the “easel” position, screens 104 and 108 are angled withrespect to each other and facing outward with the edges of screens 104and 108 substantially horizontal. In this position, device 100 can beconfigured to display information on both screens 104 and 108 to allowtwo users to simultaneously interact with device 100. When device 100 isin the “easel” position, sensors 172A and 172B generate a signalindicating that the screens 104 and 108 are positioned at an angle toeach other, and the accelerometer 176 can generate a signal indicatingthat device 100 has been placed so that the edge of screens 104 and 108are substantially horizontal. The signals can then be used incombination to generate events that trigger changes in the display ofinformation on screens 104 and 108.

FIG. 1J illustrates device 100 in a “modified easel” position. In the“modified easel” position, one of screens 104 or 108 is used as a standand is faced down on the surface of an object such as a table. Thisposition provides a convenient way for information to be displayed to auser in landscape orientation. Similar to the easel position, whendevice 100 is in the “modified easel” position, position sensors 172Aand 172B generate a signal indicating that the screens 104 and 108 arepositioned at an angle to each other. The accelerometer 176 wouldgenerate a signal indicating that device 100 has been positioned so thatone of screens 104 and 108 is faced downwardly and is substantiallyhorizontal. The signals can then be used to generate events that triggerchanges in the display of information of screens 104 and 108. Forexample, information may not be displayed on the screen that is facedown since a user cannot see the screen.

Transitional states are also possible. When the position sensors 172Aand B and/or accelerometer indicate that the screens are being closed orfolded (from open), a closing transitional state is recognized.Conversely when the position sensors 172A and B indicate that thescreens are being opened or folded (from closed), an openingtransitional state is recognized. The closing and opening transitionalstates are typically time-based, or have a maximum time duration from asensed starting point. Normally, no user input is possible when one ofthe closing and opening states is in effect. In this manner, incidentaluser contact with a screen during the closing or opening function is notmisinterpreted as user input. In embodiments, another transitional stateis possible when the device 100 is closed. This additional transitionalstate allows the display to switch from one screen 104 to the secondscreen 108 when the device 100 is closed based on some user input, e.g.,a double tap on the screen 110,114.

As can be appreciated, the description of device 100 is made forillustrative purposes only, and the embodiments are not limited to thespecific mechanical features shown in FIGS. 1A-1J and described above.In other embodiments, device 100 may include additional features,including one or more additional buttons, slots, display areas, hinges,and/or locking mechanisms. Additionally, in embodiments, the featuresdescribed above may be located in different parts of device 100 andstill provide similar functionality. Therefore, FIGS. 1A-1J and thedescription provided above are nonlimiting.

Hardware Features:

FIG. 2 illustrates components of a device 100 in accordance withembodiments of the present disclosure. In general, the device 100includes a primary screen 104 and a secondary screen 108. While theprimary screen 104 and its components are normally enabled in both theopened and closed positions or states, the secondary screen 108 and itscomponents are normally enabled in the opened state but disabled in theclosed state. However, even when in the closed state a user orapplication triggered interrupt (such as in response to a phoneapplication or camera application operation) can flip the active screen,or disable the primary screen 104 and enable the secondary screen 108,by a suitable command. Each screen 104, 108 can be touch sensitive andcan include different operative areas. For example, a first operativearea, within each touch sensitive screen 104 and 108, may comprise atouch sensitive display 110, 114. In general, the touch sensitivedisplay 110, 114 may comprise a full color, touch sensitive display. Asecond area within each touch sensitive screen 104 and 108 may comprisea gesture capture region 120, 124. The gesture capture region 120, 124may comprise an area or region that is outside of the touch sensitivedisplay 110, 114 area, and that is capable of receiving input, forexample in the form of gestures provided by a user. However, the gesturecapture region 120, 124 does not include pixels that can perform adisplay function or capability.

A third region of the touch sensitive screens 104 and 108 may comprise aconfigurable area 112, 116. The configurable area 112, 116 is capable ofreceiving input and has display or limited display capabilities. Inembodiments, the configurable area 112, 116 may present different inputoptions to the user. For example, the configurable area 112, 116 maydisplay buttons or other relatable items. Moreover, the identity ofdisplayed buttons, or whether any buttons are displayed at all withinthe configurable area 112, 116 of a touch sensitive screen 104 or 108,may be determined from the context in which the device 100 is usedand/or operated. In an exemplary embodiment, the touch sensitive screens104 and 108 comprise liquid crystal display devices extending across atleast those regions of the touch sensitive screens 104 and 108 that arecapable of providing visual output to a user, and a capacitive inputmatrix over those regions of the touch sensitive screens 104 and 108that are capable of receiving input from the user.

One or more display controllers 216 a, 216 b may be provided forcontrolling the operation of the touch sensitive screens 104 and 108,including input (touch sensing) and output (display) functions. In theexemplary embodiment illustrated in FIG. 2, a separate touch screencontroller 216 a or 216 b is provided for each touch screen 104 and 108.In accordance with alternate embodiments, a common or shared touchscreen controller 216 may be used to control each of the included touchsensitive screens 104 and 108. In accordance with still otherembodiments, the functions of a touch screen controller 216 may beincorporated into other components, such as a processor 204.

The processor 204 may comprise a general purpose programmable processoror controller for executing application programming or instructions. Inaccordance with at least some embodiments, the processor 204 may includemultiple processor cores, and/or implement multiple virtual processors.In accordance with still other embodiments, the processor 204 mayinclude multiple physical processors. As a particular example, theprocessor 204 may comprise a specially configured application specificintegrated circuit (ASIC) or other integrated circuit, a digital signalprocessor, a controller, a hardwired electronic or logic circuit, aprogrammable logic device or gate array, a special purpose computer, orthe like. The processor 204 generally functions to run programming codeor instructions implementing various functions of the device 100.

A communication device 100 may also include memory 208 for use inconnection with the execution of application programming or instructionsby the processor 204, and for the temporary or long term storage ofprogram instructions and/or data. As examples, the memory 208 maycomprise RAM, DRAM, SDRAM, or other solid state memory. Alternatively orin addition, data storage 212 may be provided. Like the memory 208, thedata storage 212 may comprise a solid state memory device or devices.Alternatively or in addition, the data storage 212 may comprise a harddisk drive or other random access memory.

In support of communications functions or capabilities, the device 100can include a cellular telephony module 228. As examples, the cellulartelephony module 228 can comprise a GSM, CDMA, FDMA and/or analogcellular telephony transceiver capable of supporting voice, multimediaand/or data transfers over a cellular network. Alternatively or inaddition, the device 100 can include an additional or other wirelesscommunications module 232. As examples, the other wirelesscommunications module 232 can comprise a Wi-Fi, BLUETOOTH™, WiMax,infrared, or other wireless communications link. The cellular telephonymodule 228 and the other wireless communications module 232 can each beassociated with a shared or a dedicated antenna 224.

A port interface 252 may be included. The port interface 252 may includeproprietary or universal ports to support the interconnection of thedevice 100 to other devices or components, such as a dock, which may ormay not include additional or different capabilities from those integralto the device 100. In addition to supporting an exchange ofcommunication signals between the device 100 and another device orcomponent, the docking port 136 and/or port interface 252 can supportthe supply of power to or from the device 100. The port interface 252also comprises an intelligent element that comprises a docking modulefor controlling communications or other interactions between the device100 and a connected device or component.

An input/output module 248 and associated ports may be included tosupport communications over wired networks or links, for example withother communication devices, server devices, and/or peripheral devices.Examples of an input/output module 248 include an Ethernet port, aUniversal Serial Bus (USB) port, Institute of Electrical and ElectronicsEngineers (IEEE) 1394, or other interface.

An audio input/output interface/device(s) 244 can be included to provideanalog audio to an interconnected speaker or other device, and toreceive analog audio input from a connected microphone or other device.As an example, the audio input/output interface/device(s) 244 maycomprise an associated amplifier and analog to digital converter.Alternatively or in addition, the device 100 can include an integratedaudio input/output device 256 and/or an audio jack for interconnectingan external speaker or microphone. For example, an integrated speakerand an integrated microphone can be provided, to support near talk orspeaker phone operations.

Hardware buttons 158 can be included for example for use in connectionwith certain control operations. Examples include a master power switch,volume control, etc., as described in conjunction with FIGS. 1A through1J. One or more image capture interfaces/devices 240, such as a camera,can be included for capturing still and/or video images. Alternativelyor in addition, an image capture interface/device 240 can include ascanner or code reader. An image capture interface/device 240 caninclude or be associated with additional elements, such as a flash orother light source.

The device 100 can also include a global positioning system (GPS)receiver 236. In accordance with embodiments of the present invention,the GPS receiver 236 may further comprise a GPS module that is capableof providing absolute location information to other components of thedevice 100. An accelerometer(s) 176 may also be included. For example,in connection with the display of information to a user and/or otherfunctions, a signal from the accelerometer 176 can be used to determinean orientation and/or format in which to display that information to theuser.

Embodiments of the present invention can also include one or moreposition sensor(s) 172. The position sensor 172 can provide a signalindicating the position of the touch sensitive screens 104 and 108relative to one another. This information can be provided as an input,for example to a user interface application, to determine an operatingmode, characteristics of the touch sensitive displays 110, 114, and/orother device 100 operations. As examples, a screen position sensor 172can comprise a series of Hall effect sensors, a multiple positionswitch, an optical switch, a Wheatstone bridge, a potentiometer, orother arrangement capable of providing a signal indicating of multiplerelative positions the touch screens are in.

Communications between various components of the device 100 can becarried by one or more buses 222. In addition, power can be supplied tothe components of the device 100 from a power source and/or powercontrol module 260. The power control module 260 can, for example,include a battery, an AC to DC converter, power control logic, and/orports for interconnecting the device 100 to an external source of power.

Device State:

FIGS. 3A and 3B represent illustrative states of device 100. While anumber of illustrative states are shown, and transitions from a firststate to a second state, it is to be appreciated that the illustrativestate diagram may not encompass all possible states and/or all possibletransitions from a first state to a second state. As illustrated in FIG.3, the various arrows between the states (illustrated by the staterepresented in the circle) represent a physical change that occurs tothe device 100, that is detected by one or more of hardware andsoftware, the detection triggering one or more of a hardware and/orsoftware interrupt that is used to control and/or manage one or morefunctions of device 100.

As illustrated in FIG. 3A, there are twelve exemplary “physical” states:closed 304, transition 308 (or opening transitional state), easel 312,modified easel 316, open 320, inbound/outbound call or communication324, image/video capture 328, transition 332 (or closing transitionalstate), landscape 340, docked 336, docked 344 and landscape 348. Next toeach illustrative state is a representation of the physical state of thedevice 100 with the exception of states 324 and 328, where the state isgenerally symbolized by the international icon for a telephone and theicon for a camera, respectfully.

In state 304, the device is in a closed state with the device 100generally oriented in the portrait direction with the primary screen 104and the secondary screen 108 back-to-back in different planes (see FIG.1H). From the closed state, the device 100 can enter, for example,docked state 336, where the device 100 is coupled with a dockingstation, docking cable, or in general docked or associated with one ormore other devices or peripherals, or the landscape state 340, where thedevice 100 is generally oriented with the primary screen 104 facing theuser, and the primary screen 104 and the secondary screen 108 beingback-to-back.

In the closed state, the device can also move to a transitional statewhere the device remains closed by the display is moved from one screen104 to another screen 108 based on a user input, e.g., a double tap onthe screen 110, 114. Still another embodiment includes a bilateralstate. In the bilateral state, the device remains closed, but a singleapplication displays at least one window on both the first display 110and the second display 114. The windows shown on the first and seconddisplay 110, 114 may be the same or different based on the applicationand the state of that application. For example, while acquiring an imagewith a camera, the device may display the view finder on the firstdisplay 110 and displays a preview for the photo subjects (full screenand mirrored left-to-right) on the second display 114.

In state 308, a transition state from the closed state 304 to thesemi-open state or easel state 312, the device 100 is shown opening withthe primary screen 104 and the secondary screen 108 being rotated arounda point of axis coincidence with the hinge. Upon entering the easelstate 312, the primary screen 104 and the secondary screen 108 areseparated from one another such that, for example, the device 100 cansit in an easel-like configuration on a surface.

In state 316, known as the modified easel position, the device 100 hasthe primary screen 104 and the secondary screen 108 in a similarrelative relationship to one another as in the easel state 312, with thedifference being one of the primary screen 104 or the secondary screen108 are placed on a surface as shown.

State 320 is the open state where the primary screen 104 and thesecondary screen 108 are generally on the same plane. From the openstate, the device 100 can transition to the docked state 344 or the openlandscape state 348. In the open state 320, the primary screen 104 andthe secondary screen 108 are generally in the portrait-like orientationwhile in landscaped state 348 the primary screen 104 and the secondaryscreen 108 are generally in a landscape-like orientation.

State 324 is illustrative of a communication state, such as when aninbound or outbound call is being received or placed, respectively, bythe device 100. While not illustrated for clarity, it should beappreciated the device 100 can transition to the inbound/outbound callstate 324 from any state illustrated in FIG. 3. In a similar manner, theimage/video capture state 328 can be entered into from any other statein FIG. 3, with the image/video capture state 328 allowing the device100 to take one or more images via a camera and/or videos with a videocapture device 240.

Transition state 322 illustratively shows primary screen 104 and thesecondary screen 108 being closed upon one another for entry into, forexample, the closed state 304.

FIG. 3B illustrates, with reference to the key, the inputs that arereceived to detect a transition from a first state to a second state. InFIG. 3B, various combinations of states are shown with in general, aportion of the columns being directed toward a portrait state 352, alandscape state 356, and a portion of the rows being directed toportrait state 360 and landscape state 364.

In FIG. 3B, the Key indicates that “H” represents an input from one ormore Hall Effect sensors, “A” represents an input from one or moreaccelerometers, “T” represents an input from a timer, “P” represents acommunications trigger input and “I” represents an image and/or videocapture request input. Thus, in the center portion 376 of the chart, aninput, or combination of inputs, are shown that represent how the device100 detects a transition from a first physical state to a secondphysical state.

As discussed, in the center portion of the chart 376, the inputs thatare received enable the detection of a transition from, for example, aportrait open state to a landscape easel state—shown in bold—“HAT.” Forthis exemplary transition from the portrait open to the landscape easelstate, a Hall Effect sensor (“H”), an accelerometer (“A”) and a timer(“T”) input may be needed. The timer input can be derived from, forexample, a clock associated with the processor.

In addition to the portrait and landscape states, a docked state 368 isalso shown that is triggered based on the receipt of a docking signal372. As discussed above and in relation to FIG. 3, the docking signalcan be triggered by the association of the device 100 with one or moreother device 100s, accessories, peripherals, smart docks, or the like.

User Interaction:

FIGS. 4A through 4H depict various graphical representations of gestureinputs that may be recognized by the screens 104, 108. The gestures maybe performed not only by a user's body part, such as a digit, but alsoby other devices, such as a stylus, that may be sensed by the contactsensing portion(s) of a screen 104, 108. In general, gestures areinterpreted differently, based on where the gestures are performed(either directly on the display 110, 114 or in the gesture captureregion 120, 124). For example, gestures in the display 110,114 may bedirected to a desktop or application, and gestures in the gesturecapture region 120, 124 may be interpreted as for the system.

With reference to FIGS. 4A-4H, a first type of gesture, a touch gesture420, is substantially stationary on the screen 104,108 for a selectedlength of time. A circle 428 represents a touch or other contact typereceived at particular location of a contact sensing portion of thescreen. The circle 428 may include a border 432, the thickness of whichindicates a length of time that the contact is held substantiallystationary at the contact location. For instance, a tap 420 (or shortpress) has a thinner border 432 a than the border 432 b for a long press424 (or for a normal press). The long press 424 may involve a contactthat remains substantially stationary on the screen for longer timeperiod than that of a tap 420. As will be appreciated, differentlydefined gestures may be registered depending upon the length of timethat the touch remains stationary prior to contact cessation or movementon the screen.

With reference to FIG. 4C, a drag gesture 400 on the screen 104,108 isan initial contact (represented by circle 428) with contact movement 436in a selected direction. The initial contact 428 may remain stationaryon the screen 104,108 for a certain amount of time represented by theborder 432. The drag gesture typically requires the user to contact anicon, window, or other displayed image at a first location followed bymovement of the contact in a drag direction to a new second locationdesired for the selected displayed image. The contact movement need notbe in a straight line but have any path of movement so long as thecontact is substantially continuous from the first to the secondlocations.

With reference to FIG. 4D, a flick gesture 404 on the screen 104,108 isan initial contact (represented by circle 428) with truncated contactmovement 436 (relative to a drag gesture) in a selected direction. Inembodiments, a flick has a higher exit velocity for the last movement inthe gesture compared to the drag gesture. The flick gesture can, forinstance, be a finger snap following initial contact. Compared to a draggesture, a flick gesture generally does not require continual contactwith the screen 104,108 from the first location of a displayed image toa predetermined second location. The contacted displayed image is movedby the flick gesture in the direction of the flick gesture to thepredetermined second location. Although both gestures commonly can movea displayed image from a first location to a second location, thetemporal duration and distance of travel of the contact on the screen isgenerally less for a flick than for a drag gesture.

With reference to FIG. 4E, a pinch gesture 408 on the screen 104,108 isdepicted. The pinch gesture 408 may be initiated by a first contact 428a to the screen 104,108 by, for example, a first digit and a secondcontact 428 b to the screen 104,108 by, for example, a second digit. Thefirst and second contacts 428 a,b may be detected by a common contactsensing portion of a common screen 104,108, by different contact sensingportions of a common screen 104 or 108, or by different contact sensingportions of different screens. The first contact 428 a is held for afirst amount of time, as represented by the border 432 a, and the secondcontact 428 b is held for a second amount of time, as represented by theborder 432 b. The first and second amounts of time are generallysubstantially the same, and the first and second contacts 428 a, bgenerally occur substantially simultaneously. The first and secondcontacts 428 a, b generally also include corresponding first and secondcontact movements 436 a, b, respectively. The first and second contactmovements 436 a, b are generally in opposing directions. Stated anotherway, the first contact movement 436 a is towards the second contact 436b, and the second contact movement 436 b is towards the first contact436 a. More simply stated, the pinch gesture 408 may be accomplished bya user's digits touching the screen 104,108 in a pinching motion.

With reference to FIG. 4F, a spread gesture 410 on the screen 104,108 isdepicted. The spread gesture 410 may be initiated by a first contact 428a to the screen 104,108 by, for example, a first digit and a secondcontact 428 b to the screen 104,108 by, for example, a second digit. Thefirst and second contacts 428 a,b may be detected by a common contactsensing portion of a common screen 104,108, by different contact sensingportions of a common screen 104,108, or by different contact sensingportions of different screens. The first contact 428 a is held for afirst amount of time, as represented by the border 432 a, and the secondcontact 428 b is held for a second amount of time, as represented by theborder 432 b. The first and second amounts of time are generallysubstantially the same, and the first and second contacts 428 a, bgenerally occur substantially simultaneously. The first and secondcontacts 428 a, b generally also include corresponding first and secondcontact movements 436 a, b, respectively. The first and second contactmovements 436 a, b are generally in a common direction. Stated anotherway, the first and second contact movements 436 a, b are away from thefirst and second contacts 428 a, b. More simply stated, the spreadgesture 410 may be accomplished by a user's digits touching the screen104,108 in a spreading motion.

The above gestures may be combined in any manner, such as those shown byFIGS. 4G and 4H, to produce a determined functional result. For example,in FIG. 4G a tap gesture 420 is combined with a drag or flick gesture412 in a direction away from the tap gesture 420. In FIG. 4H, a tapgesture 420 is combined with a drag or flick gesture 412 in a directiontowards the tap gesture 420.

The functional result of receiving a gesture can vary depending on anumber of factors, including a state of the device 100, display 110,114, or screen 104, 108, a context associated with the gesture, orsensed location of the gesture. The state of the device commonly refersto one or more of a configuration of the device 100, a displayorientation, and user and other inputs received by the device 100.Context commonly refers to one or more of the particular application(s)selected by the gesture and the portion(s) of the application currentlyexecuting, whether the application is a single- or multi-screenapplication, and whether the application is a multi-screen applicationdisplaying one or more windows in one or more screens or in one or morestacks. Sensed location of the gesture commonly refers to whether thesensed set(s) of gesture location coordinates are on a touch sensitivedisplay 110, 114 or a gesture capture region 120, 124, whether thesensed set(s) of gesture location coordinates are associated with acommon or different display or screen 104,108, and/or what portion ofthe gesture capture region contains the sensed set(s) of gesturelocation coordinates.

A tap, when received by an a touch sensitive display 110, 114, can beused, for instance, to select an icon to initiate or terminate executionof a corresponding application, to maximize or minimize a window, toreorder windows in a stack, and to provide user input such as bykeyboard display or other displayed image. A drag, when received by atouch sensitive display 110, 114, can be used, for instance, to relocatean icon or window to a desired location within a display, to reorder astack on a display, or to span both displays (such that the selectedwindow occupies a portion of each display simultaneously). A flick, whenreceived by a touch sensitive display 110, 114 or a gesture captureregion 120, 124, can be used to relocate a window from a first displayto a second display or to span both displays (such that the selectedwindow occupies a portion of each display simultaneously). Unlike thedrag gesture, however, the flick gesture is generally not used to movethe displayed image to a specific user-selected location but to adefault location that is not configurable by the user.

The pinch gesture, when received by a touch sensitive display 110, 114or a gesture capture region 120, 124, can be used to minimize orotherwise increase the displayed area or size of a window (typicallywhen received entirely by a common display), to switch windows displayedat the top of the stack on each display to the top of the stack of theother display (typically when received by different displays orscreens), or to display an application manager (a “pop-up window” thatdisplays the windows in the stack). The spread gesture, when received bya touch sensitive display 110, 114 or a gesture capture region 120, 124,can be used to maximize or otherwise decrease the displayed area or sizeof a window, to switch windows displayed at the top of the stack on eachdisplay to the top of the stack of the other display (typically whenreceived by different displays or screens), or to display an applicationmanager (typically when received by an off-screen gesture capture regionon the same or different screens).

The combined gestures of FIG. 4G, when received by a common displaycapture region in a common display or screen 104,108, can be used tohold a first window stack location in a first stack constant for adisplay receiving the gesture while reordering a second window stacklocation in a second window stack to include a window in the displayreceiving the gesture. The combined gestures of FIG. 4H, when receivedby different display capture regions in a common display or screen104,108 or in different displays or screens, can be used to hold a firstwindow stack location in a first window stack constant for a displayreceiving the tap part of the gesture while reordering a second windowstack location in a second window stack to include a window in thedisplay receiving the flick or drag gesture. Although specific gesturesand gesture capture regions in the preceding examples have beenassociated with corresponding sets of functional results, it is to beappreciated that these associations can be redefined in any manner toproduce differing associations between gestures and/or gesture captureregions and/or functional results.

Firmware and Software:

The memory 508 may store and the processor 504 may execute one or moresoftware components. These components can include at least one operatingsystem (OS) 516, an application manager 562, a desktop 566, and/or oneor more applications 564 a and/or 564 b from an application store 560.The OS 516 can include a framework 520, one or more frame buffers 548,one or more drivers 512, previously described in conjunction with FIG.2, and/or a kernel 518. The OS 516 can be any software, consisting ofprograms and data, which manages computer hardware resources andprovides common services for the execution of various applications 564.The OS 516 can be any operating system and, at least in someembodiments, dedicated to mobile devices, including, but not limited to,Linux, ANDROID™, iPhone OS (IOS™), WINDOWS PHONE 7™, etc. The OS 516 isoperable to provide functionality to the phone by executing one or moreoperations, as described herein.

The applications 564 can be any higher level software that executesparticular functionality for the user. Applications 564 can includeprograms such as email clients, web browsers, texting applications,games, media players, office suites, etc. The applications 564 can bestored in an application store 560, which may represent any memory ordata storage, and the management software associated therewith, forstoring the applications 564. Once executed, the applications 564 may berun in a different area of memory 508.

The framework 520 may be any software or data that allows the multipletasks running on the device to interact. In embodiments, at leastportions of the framework 520 and the discrete components describedhereinafter may be considered part of the OS 516 or an application 564.However, these portions will be described as part of the framework 520,but those components are not so limited. The framework 520 can include,but is not limited to, a Multi-Display Management (MDM) module 524, aSurface Cache module 528, a Window Management module 532, an InputManagement module 536, a Task Management module 540, an ApplicationModel Manager 542, a Display Controller, one or more frame buffers 548,a task stack 552, one or more window stacks 550 (which is a logicalarrangement of windows and/or desktops in a display area), and/or anevent buffer 556.

The MDM module 524 includes one or more modules that are operable tomanage the display of applications or other data on the screens of thedevice. An embodiment of the MDM module 524 is described in conjunctionwith FIG. 5B. In embodiments, the MDM module 524 receives inputs fromthe other OS 516 components, such as, the drivers 512, and from theapplications 564 to determine continually the state of the device 100.The inputs assist the MDM module 524 in determining how to configure andallocate the displays according to the application's preferences andrequirements, and the user's actions. Once a determination for displayconfigurations is made, the MDM module 524 can bind the applications 564to a display. The configuration may then be provided to one or moreother components to generate a window with a display.

The Surface Cache module 528 includes any memory or storage and thesoftware associated therewith to store or cache one or more images ofwindows. A series of active and/or non-active windows (or other displayobjects, such as, a desktop display) can be associated with eachdisplay. An active window (or other display object) is currentlydisplayed. A non-active windows (or other display objects) were openedand, at some time, displayed but are now not displayed. To enhance theuser experience, before a window transitions from an active state to aninactive state, a “screen shot” of a last generated image of the window(or other display object) can be stored. The Surface Cache module 528may be operable to store a bitmap of the last active image of a window(or other display object) not currently displayed. Thus, the SurfaceCache module 528 stores the images of non-active windows (or otherdisplay objects) in a data store.

In embodiments, the Window Management module 532 is operable to managethe windows (or other display objects) that are active or not active oneach of the displays. The Window Management module 532, based oninformation from the MDM module 524, the OS 516, or other components,determines when a window (or other display object) is visible or notactive. The Window Management module 532 may then put a non-visiblewindow (or other display object) in a “not active state” and, inconjunction with the Task Management module Task Management 540 suspendsthe application's operation. Further, the Window Management module 532may assign, through collaborative interaction with the MDM module 524, adisplay identifier to the window (or other display object) or manage oneor more other items of data associated with the window (or other displayobject). The Window Management module 532 may also provide the storedinformation to the application 564, the Task Management module 540, orother components interacting with or associated with the window (orother display object). The Window Management module 532 can alsoassociate an input task with a window based on window focus and displaycoordinates within the motion space.

The Input Management module 536 is operable to manage events that occurwith the device. An event is any input into the window environment, forexample, a user interface interactions with a user. The Input Managementmodule 536 receives the events and logically stores the events in anevent buffer 556. Events can include such user interface interactions asa “down event,” which occurs when a screen 104, 108 receives a touchsignal from a user, a “move event,” which occurs when the screen 104,108 determines that a user's finger is moving across a screen(s), an “upevent, which occurs when the screen 104, 108 determines that the userhas stopped touching the screen 104, 108, etc. These events arereceived, stored, and forwarded to other modules by the Input Managementmodule 536. The Input Management module 536 may also map screen inputsto a motion space which is the culmination of all physical and virtualdisplay available on the device.

The motion space is a virtualized space that includes all touchsensitive displays 110,114 “tiled” together to mimic the physicaldimensions of the device 100. For example, when the device 100 isunfolded, the motion space size may be 960×800, which may be the numberof pixels in the combined display area for both touch sensitive displays110, 114. If a user touches on a first touch sensitive display 110 onlocation (40, 40), a full screen window can receive touch event withlocation (40, 40). If a user touches on a second touch sensitive display114, with location (40, 40), the full screen window can receive touchevent with location (520, 40), because the second touch sensitivedisplay 114 is on the right side of the first touch sensitive display110, so the device 100 can offset the touch by the first touch sensitivedisplay's 110 width, which is 480 pixels. When a hardware event occurswith location info from a driver 512, the framework 520 can up-scale thephysical location to the motion space because the location of the eventmay be different based on the device orientation and state. The motionspace may be as described in U.S. patent application Ser. No.13/187,026, filed Jul. 20, 2011, entitled “Systems and Methods forReceiving Gesture Inputs Spanning Multiple Input Devices,” which ishereby incorporated by reference in its entirety for all that it teachesand for all purposes.

A task can be an application and a sub-task can be an applicationcomponent that provides a window with which users can interact to dosomething, such as dial the phone, take a photo, send an email, or viewa map. Each task may be given a window in which to draw a userinterface. The window typically fills a display (for example, touchsensitive display 110,114), but may be smaller than the display 110,114and float on top of other windows. An application usually consists ofmultiple sub-tasks that are loosely bound to each other. Typically, onetask in an application is specified as the “main” task, which ispresented to the user when launching the application for the first time.Each task can then start another task or sub-task to perform differentactions.

The Task Management module 540 is operable to manage the operation ofone or more applications 564 that may be executed by the device. Thus,the Task Management module 540 can receive signals to launch, suspend,terminate, etc. an application or application sub-tasks stored in theapplication store 560. The Task Management module 540 may theninstantiate one or more tasks or sub-tasks of the application 564 tobegin operation of the application 564. Further, the Task ManagementModule 540 may launch, suspend, or terminate a task or sub-task as aresult of user input or as a result of a signal from a collaboratingframework 520 component. The Task Management Module 540 is responsiblefor managing the lifecycle of applications (tasks and sub-task) fromwhen the application is launched to when the application is terminated.

The processing of the Task Management Module 540 is facilitated by atask stack 552, which is a logical structure associated with the TaskManagement Module 540. The task stack 552 maintains the state of alltasks and sub-tasks on the device 100. When some component of theoperating system 516 requires a task or sub-task to transition in itslifecycle, the OS 516 component can notify the Task Management Module540. The Task Management Module 540 may then locate the task orsub-task, using identification information, in the task stack 552, andsend a signal to the task or sub-task indicating what kind of lifecycletransition the task needs to execute. Informing the task or sub-task ofthe transition allows the task or sub-task to prepare for the lifecyclestate transition. The Task Management Module 540 can then execute thestate transition for the task or sub-task. In embodiments, the statetransition may entail triggering the OS kernel 518 to terminate the taskwhen termination is required.

Further, the Task Management module 540 may suspend the application 564based on information from the Window Management Module 532. Suspendingthe application 564 may maintain application data in memory but maylimit or stop the application 564 from rendering a window or userinterface. Once the application becomes active again, the TaskManagement module 540 can again trigger the application to render itsuser interface. In embodiments, if a task is suspended, the task maysave the task's state in case the task is terminated. In the suspendedstate, the application task may not receive input because theapplication window is not visible to the user.

The frame buffer 548 is a logical structure(s) used to render the userinterface. The frame buffer 548 can be created and destroyed by the OSkernel 518. However, the Display Controller 544 can write the imagedata, for the visible windows, into the frame buffer 548. A frame buffer548 can be associated with one screen or multiple screens. Theassociation of a frame buffer 548 with a screen can be controlleddynamically by interaction with the OS kernel 518. A composite displaymay be created by associating multiple screens with a single framebuffer 548. Graphical data used to render an application's window userinterface may then be written to the single frame buffer 548, for thecomposite display, which is output to the multiple screens 104,108. TheDisplay Controller 544 can direct an application's user interface to aportion of the frame buffer 548 that is mapped to a particular display110,114, thus, displaying the user interface on only one screen 104 or108. The Display Controller 544 can extend the control over userinterfaces to multiple applications, controlling the user interfaces foras many displays as are associated with a frame buffer 548 or a portionthereof. This approach compensates for the multiple physical screens104,108 that are in use by the software component above the DisplayController 544.

The Application Manager 562 is an application that provides apresentation layer for the window environment. Thus, the ApplicationManager 562 provides the graphical model for rendering by the TaskManagement Module 540. Likewise, the Desktop 566 provides thepresentation layer for the Application Store 560. Thus, the desktopprovides a graphical model of a surface having selectable applicationicons for the Applications 564 in the Application Store 560 that can beprovided to the Window Management Module 556 for rendering.

Further, the framework can include an Application Model Manager (AMM)542. The Application Manager 562 may interface with the AMM 542. Inembodiments, the AMM 542 receives state change information from thedevice 100 regarding the state of applications (which are running orsuspended). The AMM 542 can associate bit map images from the SurfaceCache Module 528 to the tasks that are alive (running or suspended).Further, the AMM 542 can convert the logical window stack maintained inthe Task Manager Module 540 to a linear (“film strip” or “deck ofcards”) organization that the user perceives when the using the offgesture capture area 120 to sort through the windows. Further, the AMM542 may provide a list of executing applications to the ApplicationManager 562.

An embodiment of the MDM module 524 is shown in FIG. 5B. The MDM module524 is operable to determine the state of the environment for thedevice, including, but not limited to, the orientation of the device,whether the device 100 is opened or closed, what applications 564 areexecuting, how the applications 564 are to be displayed, what actionsthe user is conducting, the tasks being displayed, etc. To configure thedisplay, the MDM module 524 interprets these environmental factors anddetermines a display configuration, as described in conjunction withFIGS. 6A-6J. Then, the MDM module 524 can bind the applications 564 orother device components to the displays. The configuration may then besent to the Display Controller 544 and/or the other components withinthe OS 516 to generate the display. The MDM module 524 can include oneor more of, but is not limited to, a Display Configuration Module 568, aPreferences Module 572, a Device State Module 574, a Gesture Module 576,a Requirements Module 580, an Event Module 584, and/or a Binding Module588.

The Display Configuration Module 568 determines the layout for thedisplay. In embodiments, the Display Configuration Module 568 candetermine the environmental factors. The environmental factors may bereceived from one or more other MDM modules 524 or from other sources.The Display Configuration Module 568 can then determine from the list offactors the best configuration for the display. Some embodiments of thepossible configurations and the factors associated therewith aredescribed in conjunction with FIGS. 6A-6F.

The Preferences Module 572 is operable to determine display preferencesfor an application 564 or other component. For example, an applicationcan have a preference for Single or Dual displays. The PreferencesModule 572 can determine an application's display preference (e.g., byinspecting the application's preference settings) and may allow theapplication 564 to change to a mode (e.g., single screen, dual screen,max, etc.) if the device 100 is in a state that can accommodate thepreferred mode. However, some user interface policies may disallow amode even if the mode is available. As the configuration of the devicechanges, the preferences may be reviewed to determine if a betterdisplay configuration can be achieved for an application 564.

The Device State Module 574 is operable to determine or receive thestate of the device. The state of the device can be as described inconjunction with FIGS. 3A and 3B. The state of the device can be used bythe Display Configuration Module 568 to determine the configuration forthe display. As such, the Device State Module 574 may receive inputs andinterpret the state of the device. The state information is thenprovided to the Display Configuration Module 568.

The Gesture Module 576 is shown as part of the MDM module 524, but, inembodiments, the Gesture module 576 may be a separate Framework 520component that is separate from the MDM module 524. In embodiments, theGesture Module 576 is operable to determine if the user is conductingany actions on any part of the user interface. In alternativeembodiments, the Gesture Module 576 receives user interface actions fromthe configurable area 112,116 only. The Gesture Module 576 can receivetouch events that occur on the configurable area 112,116 (or possiblyother user interface areas) by way of the Input Management Module 536and may interpret the touch events (using direction, speed, distance,duration, and various other parameters) to determine what kind ofgesture the user is performing. When a gesture is interpreted, theGesture Module 576 can initiate the processing of the gesture and, bycollaborating with other Framework 520 components, can manage therequired window animation. The Gesture Module 576 collaborates with theApplication Model Manager 542 to collect state information with respectto which applications are running (active or paused) and the order inwhich applications must appear when a user gesture is performed. TheGesture Module 576 may also receive references to bitmaps (from theSurface Cache Module 528) and live windows so that when a gesture occursit can instruct the Display Controller 544 how to move the window(s)across the display 110,114. Thus, suspended applications may appear tobe running when those windows are moved across the display 110,114.

Further, the Gesture Module 576 can receive task information either fromthe Task Manage Module 540 or the Input Management module 536. Thegestures may be as defined in conjunction with FIGS. 4A through 4H. Forexample, moving a window causes the display to render a series ofdisplay frames that illustrate the window moving. The gesture associatedwith such user interface interaction can be received and interpreted bythe Gesture Module 576. The information about the user gesture is thensent to the Task Management Module 540 to modify the display binding ofthe task.

The Requirements Module 580, similar to the Preferences Module 572, isoperable to determine display requirements for an application 564 orother component. An application can have a set display requirement thatmust be observed. Some applications require a particular displayorientation. For example, the application “Angry Birds” can only bedisplayed in landscape orientation. This type of display requirement canbe determined or received, by the Requirements Module 580. As theorientation of the device changes, the Requirements Module 580 canreassert the display requirements for the application 564. The DisplayConfiguration Module 568 can generate a display configuration that is inaccordance with the application display requirements, as provided by theRequirements Module 580.

The Event Module 584, similar to the Gesture Module 576, is operable todetermine one or more events occurring with an application or othercomponent that can affect the user interface. Thus, the Event Module 584can receive event information either from the event buffer 556 or theTask Management module 540. These events can change how the tasks arebound to the displays. The Event Module 584 can collect state changeinformation from other Framework 520 components and act upon that statechange information. In an example, when the phone is opened or closed orwhen an orientation change has occurred, a new message may be renderedin a secondary screen. The state change based on the event can bereceived and interpreted by the Event Module 584. The information aboutthe events then may be sent to the Display Configuration Module 568 tomodify the configuration of the display.

The Binding Module 588 is operable to bind the applications 564 or theother components to the configuration determined by the DisplayConfiguration Module 568. A binding associates, in memory, the displayconfiguration for each application with the display and mode of theapplication. Thus, the Binding Module 588 can associate an applicationwith a display configuration for the application (e.g. landscape,portrait, multi-screen, etc.). Then, the Binding Module 588 may assign adisplay identifier to the display. The display identifier associated theapplication with a particular display of the device 100. This binding isthen stored and provided to the Display Controller 544, the othercomponents of the OS 516, or other components to properly render thedisplay. The binding is dynamic and can change or be updated based onconfiguration changes associated with events, gestures, state changes,application preferences or requirements, etc.

User Interface Configurations:

With reference now to FIGS. 6A-J, various types of output configurationsmade possible by the device 100 will be described hereinafter.

FIGS. 6A and 6B depict two different output configurations of the device100 being in a first state. Specifically, FIG. 6A depicts the device 100being in a closed portrait state 304 where the data is displayed on theprimary screen 104. In this example, the device 100 displays data viathe touch sensitive display 110 in a first portrait configuration 604.As can be appreciated, the first portrait configuration 604 may onlydisplay a desktop or operating system home screen. Alternatively, one ormore windows may be presented in a portrait orientation while the device100 is displaying data in the first portrait configuration 604.

FIG. 6B depicts the device 100 still being in the closed portrait state304, but instead data is displayed on the secondary screen 108. In thisexample, the device 100 displays data via the touch sensitive display114 in a second portrait configuration 608.

It may be possible to display similar or different data in either thefirst or second portrait configuration 604, 608. It may also be possibleto transition between the first portrait configuration 604 and secondportrait configuration 608 by providing the device 100 a user gesture(e.g., a double tap gesture), a menu selection, or other means. Othersuitable gestures may also be employed to transition betweenconfigurations. Furthermore, it may also be possible to transition thedevice 100 from the first or second portrait configuration 604, 608 toany other configuration described herein depending upon which state thedevice 100 is moved.

An alternative output configuration may be accommodated by the device100 being in a second state. Specifically, FIG. 6C depicts a thirdportrait configuration where data is displayed simultaneously on boththe primary screen 104 and the secondary screen 108. The third portraitconfiguration may be referred to as a Dual-Portrait (PD) outputconfiguration. In the PD output configuration, the touch sensitivedisplay 110 of the primary screen 104 depicts data in the first portraitconfiguration 604 while the touch sensitive display 114 of the secondaryscreen 108 depicts data in the second portrait configuration 608. Thesimultaneous presentation of the first portrait configuration 604 andthe second portrait configuration 608 may occur when the device 100 isin an open portrait state 320. In this configuration, the device 100 maydisplay one application window in one display 110 or 114, twoapplication windows (one in each display 110 and 114), one applicationwindow and one desktop, or one desktop. Other configurations may bepossible. It should be appreciated that it may also be possible totransition the device 100 from the simultaneous display ofconfigurations 604, 608 to any other configuration described hereindepending upon which state the device 100 is moved. Furthermore, whilein this state, an application's display preference may place the deviceinto bilateral mode, in which both displays are active to displaydifferent windows in the same application. For example, a Cameraapplication may display a viewfinder and controls on one side, while theother side displays a mirrored preview that can be seen by the photosubjects. Games involving simultaneous play by two players may also takeadvantage of bilateral mode.

FIGS. 6D and 6E depicts two further output configurations of the device100 being in a third state. Specifically, FIG. 6D depicts the device 100being in a closed landscape state 340 where the data is displayed on theprimary screen 104. In this example, the device 100 displays data viathe touch sensitive display 110 in a first landscape configuration 612.Much like the other configurations described herein, the first landscapeconfiguration 612 may display a desktop, a home screen, one or morewindows displaying application data, or the like.

FIG. 6E depicts the device 100 still being in the closed landscape state340, but instead data is displayed on the secondary screen 108. In thisexample, the device 100 displays data via the touch sensitive display114 in a second landscape configuration 616. It may be possible todisplay similar or different data in either the first or second portraitconfiguration 612, 616. It may also be possible to transition betweenthe first landscape configuration 612 and second landscape configuration616 by providing the device 100 with one or both of a twist and tapgesture or a flip and slide gesture. Other suitable gestures may also beemployed to transition between configurations. Furthermore, it may alsobe possible to transition the device 100 from the first or secondlandscape configuration 612, 616 to any other configuration describedherein depending upon which state the device 100 is moved.

FIG. 6F depicts a third landscape configuration where data is displayedsimultaneously on both the primary screen 104 and the secondary screen108. The third landscape configuration may be referred to as aDual-Landscape (LD) output configuration. In the LD outputconfiguration, the touch sensitive display 110 of the primary screen 104depicts data in the first landscape configuration 612 while the touchsensitive display 114 of the secondary screen 108 depicts data in thesecond landscape configuration 616. The simultaneous presentation of thefirst landscape configuration 612 and the second landscape configuration616 may occur when the device 100 is in an open landscape state 340. Itshould be appreciated that it may also be possible to transition thedevice 100 from the simultaneous display of configurations 612, 616 toany other configuration described herein depending upon which state thedevice 100 is moved.

FIGS. 6G and 6H depict two views of a device 100 being in yet anotherstate. Specifically, the device 100 is depicted as being in an easelstate 312. FIG. 6G shows that a first easel output configuration 618 maybe displayed on the touch sensitive display 110. FIG. 6H shows that asecond easel output configuration 620 may be displayed on the touchsensitive display 114. The device 100 may be configured to depict eitherthe first easel output configuration 618 or the second easel outputconfiguration 620 individually. Alternatively, both the easel outputconfigurations 618, 620 may be presented simultaneously. In someembodiments, the easel output configurations 618, 620 may be similar oridentical to the landscape output configurations 612, 616. The device100 may also be configured to display one or both of the easel outputconfigurations 618, 620 while in a modified easel state 316. It shouldbe appreciated that simultaneous utilization of the easel outputconfigurations 618, 620 may facilitate two-person games (e.g.,Battleship®, chess, checkers, etc.), multi-user conferences where two ormore users share the same device 100, and other applications. As can beappreciated, it may also be possible to transition the device 100 fromthe display of one or both configurations 618, 620 to any otherconfiguration described herein depending upon which state the device 100is moved.

FIG. 6I depicts yet another output configuration that may beaccommodated while the device 100 is in an open portrait state 320.Specifically, the device 100 may be configured to present a singlecontinuous image across both touch sensitive displays 110, 114 in aportrait configuration referred to herein as a Portrait-Max (PMax)configuration 624. In this configuration, data (e.g., a single image,application, window, icon, video, etc.) may be split and displayedpartially on one of the touch sensitive displays while the other portionof the data is displayed on the other touch sensitive display. The Pmaxconfiguration 624 may facilitate a larger display and/or betterresolution for displaying a particular image on the device 100. Similarto other output configurations, it may be possible to transition thedevice 100 from the Pmax configuration 624 to any other outputconfiguration described herein depending upon which state the device 100is moved.

FIG. 6J depicts still another output configuration that may beaccommodated while the device 100 is in an open landscape state 348.Specifically, the device 100 may be configured to present a singlecontinuous image across both touch sensitive displays 110, 114 in alandscape configuration referred to herein as a Landscape-Max (LMax)configuration 628. In this configuration, data (e.g., a single image,application, window, icon, video, etc.) may be split and displayedpartially on one of the touch sensitive displays while the other portionof the data is displayed on the other touch sensitive display. The Lmaxconfiguration 628 may facilitate a larger display and/or betterresolution for displaying a particular image on the device 100. Similarto other output configurations, it may be possible to transition thedevice 100 from the Lmax configuration 628 to any other outputconfiguration described herein depending upon which state the device 100is moved.

The device 100 manages desktops and/or windows with at least one windowstack 700, 728, as shown in FIGS. 7A and 7B. A window stack 700, 728 isa logical arrangement of active and/or inactive windows for amulti-screen device. For example, the window stack 700, 728 may belogically similar to a deck of cards, where one or more windows ordesktops are arranged in order, as shown in FIGS. 7A and 7B. An activewindow is a window that is currently being displayed on at least one ofthe touch sensitive displays 110, 114. For example, windows 104 and 108are active windows and are displayed on touch sensitive displays 110 and114. An inactive window is a window that was opened and displayed but isnow “behind” an active window and not being displayed. In embodiments,an inactive window may be for an application that is suspended, andthus, the window is not displaying active content. For example, windows712, 716, 720, and 724 are inactive windows.

A window stack 700, 728 may have various arrangements or organizationalstructures. In the embodiment shown in FIG. 7A, the device 100 includesa first stack 760 associated with a first touch sensitive display 110and a second stack associated with a second touch sensitive display 114.Thus, each touch sensitive display 110, 114 can have an associatedwindow stack 760, 764. These two window stacks 760, 764 may havedifferent numbers of windows arranged in the respective stacks 760, 764.Further, the two window stacks 760, 764 can also be identifieddifferently and managed separately. Thus, the first window stack 760 canbe arranged in order from a first window 704 to a next window 720 to alast window 724 and finally to a desktop 722, which, in embodiments, isat the “bottom” of the window stack 760. In embodiments, the desktop 722is not always at the “bottom” as application windows can be arranged inthe window stack below the desktop 722, and the desktop 722 can bebrought to the “top” of a stack over other windows during a desktopreveal Likewise, the second stack 764 can be arranged from a firstwindow 708 to a next window 712 to a last window 716, and finally to adesktop 718, which, in embodiments, is a single desktop area, withdesktop 722, under all the windows in both window stack 760 and windowstack 764. A logical data structure for managing the two window stacks760, 764 may be as described in conjunction with FIG. 8.

Another arrangement for a window stack 728 is shown in FIG. 7B. In thisembodiment, there is a single window stack 728 for both touch sensitivedisplays 110, 114. Thus, the window stack 728 is arranged from a desktop758 to a first window 744 to a last window 756. A window can be arrangedin a position among all windows without an association to a specifictouch sensitive display 110, 114. In this embodiment, a window is in theorder of windows. Further, at least one window is identified as beingactive. For example, a single window may be rendered in two portions 732and 736 that are displayed on the first touch sensitive screen 110 andthe second touch sensitive screen 114. The single window may only occupya single position in the window stack 728 although it is displayed onboth displays 110, 114.

Yet another arrangement of a window stack 760 is shown in FIGS. 7Cthrough 7E. The window stack 760 is shown in three “elevation” views. InFIG. 7C, the top of the window stack 760 is shown. Two sides of thewindow stack 760 are shown in FIGS. 7D and 7E. In this embodiment, thewindow stack 760 resembles a stack of bricks. The windows are stacked oneach other. Looking from the top of the window stack 760 in FIG. 7C,only the top most windows in the window stack 760 are seen in differentportions of the composite display 764. The composite display 764represents a logical model for the entire display area of the device100, which can include touch sensitive display 110 and touch sensitivedisplay 114. A desktop 786 or a window can occupy part or all of thecomposite display 764.

In the embodiment shown, the desktop 786 is the lowest display or“brick” in the window stack 760. Thereupon, window 1 782, window 2 782,window 3 768, and window 4 770 are layered. Window 1 782, window 3 768,window 2 782, and window 4 770 only occupy a portion of the compositedisplay 764. Thus, another part of the stack 760 includes window 8 774and windows 5 through 7 shown in section 790. Only the top window in anyportion of the composite display 764 is actually rendered and displayed.Thus, as shown in the top view in FIG. 7C, window 4 770, window 8 774,and window 3 768 are displayed as being at the top of the display indifferent portions of the window stack 760. A window can be dimensionedto occupy only a portion of the composite display 760 to “reveal”windows lower in the window stack 760. For example, window 3 768 islower in the stack than both window 4 770 and window 8 774 but is stilldisplayed. A logical data structure to manage the window stack can be asdescribed in conjunction with FIG. 8.

When a new window is opened, the newly activated window is generallypositioned at the top of the stack. However, where and how the window ispositioned within the stack can be a function of the orientation of thedevice 100, the context of what programs, functions, software, etc. arebeing executed on the device 100, how the stack is positioned when thenew window is opened, etc. To insert the window in the stack, theposition in the stack for the window is determined and the touchsensitive display 110, 114 to which the window is associated may also bedetermined. With this information, a logical data structure for thewindow can be created and stored. When user interface or other events ortasks change the arrangement of windows, the window stack(s) can bechanged to reflect the change in arrangement. It should be noted thatthese same concepts described above can be used to manage the one ormore desktops for the device 100.

A logical data structure 800 for managing the arrangement of windows ordesktops in a window stack is shown in FIG. 8. The logical datastructure 800 can be any data structure used to store data whether anobject, record, file, etc. The logical data structure 800 can be storedin any type of database or data storage system, regardless of protocolor standard. In embodiments, the logical data structure 800 includes oneor more portions, fields, attributes, etc. that store data in a logicalarrangement that allows for easy storage and retrieval of theinformation. Hereinafter, these one or more portions, fields,attributes, etc. shall be described simply as fields. The fields canstore data for a window identifier 804, dimensions 808, a stack positionidentifier 812, a display identifier 816, and/or an active indicator820. Each window in a window stack can have an associated logical datastructure 800. While only a single logical data structure 800 is shownin FIG. 8, there may be more or fewer logical data structures 800 usedwith a window stack (based on the number of windows or desktops in thestack), as represented by ellipses 824. Further, there may be more orfewer fields than those shown in FIG. 8, as represented by ellipses 828.

A window identifier 804 can include any identifier (ID) that uniquelyidentifies the associated window in relation to other windows in thewindow stack. The window identifier 804 can be a globally uniqueidentifier (GUID), a numeric ID, an alphanumeric ID, or other type ofidentifier. In embodiments, the window identifier 804 can be one, two,or any number of digits based on the number of windows that can beopened. In alternative embodiments, the size of the window identifier804 may change based on the number of windows opened. While the windowis open, the window identifier 804 may be static and remain unchanged.

Dimensions 808 can include dimensions for a window in the compositedisplay 760. For example, the dimensions 808 can include coordinates fortwo or more corners of the window or may include one coordinate anddimensions for the width and height of the window. These dimensions 808can delineate what portion of the composite display 760 the window mayoccupy, which may the entire composite display 760 or only part ofcomposite display 760. For example, window 4 770 may have dimensions 880that indicate that the window 770 will occupy only part of the displayarea for composite display 760, as shown in FIGS. 7 c through 7E. Aswindows are moved or inserted in the window stack, the dimensions 808may change.

A stack position identifier 812 can be any identifier that can identifythe position in the stack for the window or may be inferred from thewindow's control record within a data structure, such as a list or astack. The stack position identifier 812 can be a GUID, a numeric ID, analphanumeric ID, or other type of identifier. Each window or desktop caninclude a stack position identifier 812. For example, as shown in FIG.7A, window 1 704 in stack 1 760 can have a stack position identifier 812of 1 identifying that window 704 is the first window in the stack 760and the active window. Similarly, window 6 724 can have a stack positionidentifier 812 of 3 representing that window 724 is the third window inthe stack 760. Window 2 708 can also have a stack position identifier812 of 1 representing that window 708 is the first window in the secondstack 764. As shown in FIG. 7B, window 1 744 can have a stack positionidentifier 812 of 1, window 3, rendered in portions 732 and 736, canhave a stack position identifier 812 of 3, and window 6 756 can have astack position identifier 812 of 6. Thus, depending on the type ofstack, the stack position identifier 812 can represent a window'slocation in the stack.

A display identifier 816 can identify that the window or desktop isassociated with a particular display, such as the first display 110 orthe second display 114, or the composite display 760 composed of bothdisplays. While this display identifier 816 may not be needed for amulti-stack system, as shown in FIG. 7A, the display identifier 816 canindicate whether a window in the serial stack of FIG. 7B is displayed ona particular display. Thus, window 3 may have two portions 732 and 736in FIG. 7B. The first portion 732 may have a display identifier 816 forthe first display while the second portion 736 may have a displayidentifier 816 for the second display 114. However, in alternativeembodiments, the window may have two display identifier 816 thatrepresent that the window is displayed on both of the displays 110, 114,or a display identifier 816 identifying the composite display. Inanother alternate embodiment, the window may have a single displayidentifier 816 to represent that the window is displayed on both of thedisplays 110, 114.

Similar to the display identifier 816, an active indicator 820 may notbe needed with the dual stack system of FIG. 7A, as the window in stackposition 1 is active and displayed. In the system of FIG. 7B, the activeindicator 820 can indicate which window(s) in the stack is beingdisplayed. Thus, window 3 may have two portions 732 and 736 in FIG. 7.The first portion 732 may have an active indicator 820 while the secondportion 736 may also have an active indicator 820. However, inalternative embodiments, window 3 may have a single active indicator820. The active indicator 820 can be a simple flag or bit thatrepresents that the window is active or displayed.

An embodiment of a method 900 for creating a window stack is shown inFIG. 9. While a general order for the steps of the method 900 is shownin FIG. 9. Generally, the method 900 starts with a start operation 904and ends with an end operation 928. The method 900 can include more orfewer steps or can arrange the order of the steps differently than thoseshown in FIG. 9. The method 900 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method900 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-8.

A multi-screen device 100 can receive activation of a window, in step908. In embodiments, the multi-screen device 100 can receive activationof a window by receiving an input from the touch sensitive display 110or 114, the configurable area 112 or 116, a gesture capture region 120or 124, or some other hardware sensor operable to receive user interfaceinputs. The processor may execute the Task Management Module 540 mayreceive the input. The Task Management Module 540 can interpret theinput as requesting an application task to be executed that will open awindow in the window stack.

In embodiments, the Task Management Module 540 places the user interfaceinteraction in the task stack 552 to be acted upon by the DisplayConfiguration Module 568 of the Multi-Display Management Module 524.Further, the Task Management Module 540 waits for information from theMulti-Display Management Module 524 to send instructions to the WindowManagement Module 532 to create the window in the window stack.

The Multi-Display Management Module 524, upon receiving instruction fromthe Task Management Module 540, determines to which touch portion of thecomposite display 760, the newly activated window should be associated,in step 912. For example, window 4 770 is associated with the a portionof the composite display 764 In embodiments, the device state module 574of the Multi-Display Management Module 524 may determine how the deviceis oriented or in what state the device is in, e.g., open, closed,portrait, etc. Further, the preferences module 572 and/or requirementsmodule 580 may determine how the window is to be displayed. The gesturemodule 576 may determine the user's intentions about how the window isto be opened based on the type of gesture and the location of where thegesture is made.

The Display Configuration Module 568 may use the input from thesemodules and evaluate the current window stack 760 to determine the bestplace and the best dimensions, based on a visibility algorithm, to openthe window. Thus, the Display Configuration Module 568 determines thebest place to put the window at the top of the window stack 760, in step916. The visibility algorithm, in embodiments, determines for allportions of the composite display, which windows are at the top of thestack. For example, the visibility algorithm determines that window 3768, window 4 770, and window 8 774 are at the top of the stack 760 asviewed in FIGS. 7C through 7E. Upon determining where to open thewindow, the Display Configuration Module 568 can assign a displayidentifier 816 and possibly dimensions 808 to the window. The displayidentifier 816 and dimensions 808 can then be sent back to the TaskManagement Module 540. The Task Management Module 540 may then assignthe window a stack position identifier 812 indicating the windowsposition at the top of the window stack.

In embodiments, the Task Management Module 540 sends the window stackinformation and instructions to render the window to the WindowManagement Module 532. The Window Management Module 532 and the TaskManagement Module 540 can create the logical data structure 800, in step924. Both the Task Management Module 540 and the Window ManagementModule 532 may create and manage copies of the window stack. Thesecopies of the window stack can be synchronized or kept similar throughcommunications between the Window Management Module 532 and the TaskManagement Module 540. Thus, the Window Management Module 532 and theTask Management Module 540, based on the information determined by theMulti-Display Management Module 524, can assign dimensions 808, a stackposition identifier 812 (e.g., window 1 782, window 4 770, etc.), adisplay identifier 816 (e.g., touch sensitive display 1 110, touchsensitive display 2 114, composite display identifier, etc,), and anactive indicator 820, which is generally always set when the window isat the “top” of the stack. The logical data structure 800 may then bestored by both the Window Management Module 532 and the Task ManagementModule 540. Further, the Window Management Module 532 and the TaskManagement Module 540 may thereinafter manage the window stack and thelogical data structure(s) 800.

An embodiment of a method 1000 for executing an application is shown inFIG. 10. While a general order for the steps of the method 1000 is shownin FIG. 10. Generally, the method 1000 starts with a start operation1004 and ends with an end operation 1040. The method 1000 can includemore or fewer steps or can arrange the order of the steps differentlythan those shown in FIG. 10. The method 1000 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method1000 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-9.

An application is executed, in step 1008. In embodiments, a processor204 receives indication to execute an application through a userinterface 110, 114, 112, 116, etc. The indication can be a selection ofan icon associated with the application. In other embodiments, theindication can be a signal generated from another application or event,such as receiving an e-mail or other communication, which causes theapplication to execute automatically. The processor 204 can retrieve theapplication 564 a from the application store 560 and begin itsexecution. In executing the application 564 a, a user interface can begenerated for a user, as described in conjunction with FIGS. 11-61D.

In creating a user interface, the application 564 a can begin executingto create a manifest, in step 1012. A manifest is a data structure thatindicates the capabilities of the application 564 a. The manifest cangenerally be created from the resources in the resources directory ofthe application 564 a. The resources directory can indicate the types ofmodes, locations, or other indications for how the user interface shouldbe configured in the multi-display device 100. For example, the severalmodes can include: “classic mode” that indicates that the application564 a is capable of being displayed on a single screen or display110/114; “dual mode” that indicates that the application 564 a iscapable of being displaced on two or more displays 110 and 114; “maxmode” that indicates the application 564 a is capable of being displayedor desires to be displayed across multiple displays 110 and 114; and/or“bilateral mode” that indicates that the application 564 a is capable ofbeing displayed on 2 or more displays 110 and 114 when the device 100 isin easel mode (see FIGS. 1I and/or 1J).

Similarly, the manifest can include a desired or allowed location withinthe displays 110/114. The possible locations can include: “left”, whichindicates that the application 564 a desires to be displayed on the leftdisplay 110; “right”, which indicates that the application 564 a desiresto be displayed on the right display 114; and/or other indications ofwhere a location should be including possible “top” and/or “bottom” ofone or more of the displays 110/114.

The application 564 a can also indicate that it desires to be displayedin a “minimum” window, which is a window that occupies less than thefull area of a single display. There may be other modes possible for theapplication 564 a, which may be included in the manifest. The manifestcan be sent from the application 564 a to the multi-display managementmodule 524.

The multi-display management module 524 can receive the manifest, instep 1016. In receiving the manifest, the multi-display managementmodule 524 can use the information to determine a display binding forthe application 564 a. The manifest may be received more than once fromthe application 564 a based on changes in how the application 564 a isbeing executed, where the application 564 a desires to have a differentdisplay setting for the new mode. Thus, with the manifest, theapplication 564 a can indicate to the multi-display management module524 how best to or what is the desired for the application's userinterface. The multi-display management module 524 can use theinformation in the manifest to determine the best fit for the userinterface depending on how the device 100 is currently configured.

The multi-display management module 524 can determine the applicationdisplay mode, in step 1020. Here the multi-display management module 524receives or retrieves an indication of the device 100 configuration. Forexample, the multi-display management module 524 can determine if thedevice is in single display configuration (see FIG. 6A, 6B, 6D, or 6E),dual display configuration (see FIG. 6C or 6F), bilateral displayconfiguration (see FIG. 6G or 6H), or one of the other displayconfigurations (see FIG. 6I or 6J).

Further, the multi-display management module 524 can determine if thedevice 100 is in a portrait or landscape orientation. With thisinformation, the multi-display management module 524 may then considerthe capabilities or preferences listed for the application 564 a in thereceived manifest. The combined information may then allow themulti-display management module 524 to determine a display binding. Thedisplay binding can include which of the one or more displays 110 and/or114 are going to be used to display the application's user interface(s).For example, the multi-display management module 524 can determine thatthe primary display 110, the secondary display 114, or all displays 110and 114 of the device 100 will be used to display the application's userinterface.

The display modes setting can be assigned by creating or setting anumber in the display binding. This number can be “0” for the primarydisplay 110, “1” for the secondary display 114, or “2” for dual displays110 and 114. The display mode setting can also indicate if theapplication 564 a should display the user interface in portrait orlandscape orientation. Further, there may be other settings, forexample, providing a max mode or other setting that may indicate how theapplication 564 a is to be displayed on the device. The display bindinginformation is stored in a data structure to create and set a binding,in step 1024.

The established display binding may then be provided, by themulti-display management module 524, to the application 564 a, in step1028. The provided display binding data structure can become anattribute of the application 564 a. An application 564 a maythereinafter store the display binding attribute in the memory of thedevice 100. The application 564 a with the display binding may thengenerate a user interface based on this display binding. The application564 a may be unaware of the position of the display 110/114 but may,from the display binding, be able to determine the size of the availableuser interface to generate a window that has particular characteristicsfor that display setting.

When a configuration change happens to the device 100, the multi-displaymanagement module 524 may change the display binding and send a newdisplay binding to the application 564 a. In embodiments, themulti-display management module 524 may indicate to the application 564a that there is a new binding or, in other embodiments, the application564 a may request a display configuration change or a new displaybinding, in which case the multi-display management module 524 may senda new display binding to the application 564 a. Thus, the multi-displaymanagement module 524 can change the configuration of the display forthe application 564 a by altering the display binding for theapplication 564 a during the execution of that application 564 a.

The multi-display management module 524 thereinafter, while theapplication 564 a is executing, can determine if there has been aconfiguration change to the device 100, in step 1032. The configurationchange may be an event (see FIGS. 3A and 3B) triggered by one or moresignals from one or more hardware sensor 172, 176, etc. For example, ifthe device 100 is changed from portrait 304 to landscape 340orientation, Hall effect sensors 172 may indicate to the framework 520that a display configuration change has been made. Other changes mayinclude transitions from a single display 304 to a dual displayconfiguration 320, by opening the device. Other types of configurationchanges may be possible and may be signaled to alert the multi-displaymanagement module 524 of the configuration change. If a configurationchange has been made, the method 1000 proceeds YES to step 1020 so thatthe multi-display management module 524 can determine new applicationdisplay mode settings and create a new display binding, which may bepassed to the application 564 a. If there are no configuration changes,the method 1000 precedes NO to step 1036.

In step 1036, a new application mode change may be determined.Application mode changes can also occur in the application 564 a, andthus, the application 564 a can determine if something has occurredwithin the application 564 a that requires a different display setting.Modes are described hereinafter with respect to FIG. 12. The mode changecan create a desire to change the display 110/114, and thus, require theapplication 564 a to generate a new manifest. If the application 564 adoes sense a mode change or an event has occurred that requires a changein display setting, the method 1000 proceeds YES back to step 1012. Atstep 1012, a new manifest or preference is created by the application564 a that may be received by the multi-display management module 524 todetermine if the multi-display management module 524 can change thedisplay binding. If it is possible to provide the preferred display, themulti-display management module 524 can create a new display binding andsend display binding back to the application 564 a and allow theapplication 564 a to alter its user interface. If no mode change issensed or an event is not received to create a mode change, the method1000 proceeds NO to end operation 1040.

An embodiment of a method 1100 for executing an application is shown inFIG. 11. While a general order for the steps of the method 1100 is shownin FIG. 11. Generally, the method 1100 starts with a start operation1104 and ends with an end operation 1116. The method 1100 can includemore or fewer steps or can arrange the order of the steps differentlythan those shown in FIG. 11. The method 1100 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method1100 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-10.

Method 1100 begins when a device 100 is provided. The device 100includes a touch sensitive display 110 and a second touch sensitivedisplay 114. The device 100 can include an off-screen gesture area. Anoff-screen gesture area is an area that is not part of the touchsensitive displays 110, 114 that can accept user interface input. Theoff-screen gesture area may include gesture capture regions 120, 124.Thus, the off-screen gesture area can function similarly to the gesturecapture region 120, 124 but may encompass both of the gesture captureregion 120, 124.

Referring again to method 1100, a user interface input is received in anoff-screen gesture area, in step 1108. The gesture may be any gesturesdescribed in conjunction with FIGS. 4A through 4H. The gestures canaffect how the device 100 operates or executes applications and/or howthe device 100 displays information on the touch sensitive display 110and/or the second touch sensitive display 114.

In response to the user interface input, the device 100 changes thedisplay on either the touch sensitive display 110 or the second touchsensitive display 114, in step 1112. In some circumstances, the displaysin both the first and second touch sensitive display 114 110, 114 arechanged. Examples of different gestures received in the off-screengesture area and how those changes may occur to the display(s) are shownin conjunction with FIGS. 12 through 14.

For example, in FIG. 12, a series of interactions 1200 is shown. Adevice 100 may have a first configuration 1204, with the touch sensitivedisplay 110 displaying a first application 1208. The second touchsensitive display 114 may be displaying a desktop or a secondapplication window 1212. The user may enter a user interface input 1216as shown in scene 1216 in the off-screen gesture area 1220, which isabove the touch sensitive display 110 and/or the second touch sensitivedisplay 114.

In this example, the gesture 1216 could be a flick gesture, as describedin conjunction with FIG. 4D, a drag gesture, as described in conjunctionwith FIG. 4B, or some other gesture. The gesture may cause a window 1208or display within one of the touch sensitive display 110 or second touchsensitive display 114 to change position. For example, the change ofdisplay may be a movement of a window 1208 from a touch sensitivedisplay 110 to a second touch sensitive display 114 as shown inscenarios 1220, 1224, and 1228. Here, a drag gesture shown across theoff-screen gesture area (e.g., box 1232) containing gesture captureregion 120 and gesture capture region 124 that causes window 1208 tomove from a touch sensitive display 110 to a second touch sensitivedisplay 114.

In FIG. 13, two scenarios are shown 1304 and 1308. In the first scenario1304, a user uses a flick gesture to move a window 1316 from a touchsensitive display 110 to a second touch sensitive display 114. In asecond scenario 1308, the user begins a flick gesture on a touchsensitive display 110; however, the flick gesture does not cross overinto the gesture capture region 124. Rather, the user picks up theirfinger and ends the gesture before moving off the gesture capture region120. This stopping of the gesture is shown in scene 1312.

If the gesture does not cross over into the second gesture captureregion 124, the movement is not completed. The device 100 can determineif a movement is completed and, if so, can complete the display actionas shown in scenario 1304. However, if the movement is not completed orgesture is stopped, as shown in scenario 1312, the window 1316 may bereturned to the touch sensitive display 110, as shown in scenes 1324 and1320.

In still other scenarios, a gesture in a second gesture capture region124 of the off-screen gesture area 1232 may cause a different type ofdisplay change. For example, in scenario 1404, a user may begin a draggesture in the off-screen gesture area 1232 of a second touch sensitivedisplay 114. This second gesture may show a second window or window icon1408 moving onto the second touch sensitive display 114. The user maythen move the second touch sensitive display icon but if the user doesnot complete the gesture by moving further to the right of the gesturecapture region 124, the window 1408 or window icon may be returned tothe touch sensitive display 110.

However, as shown in scenario 1416, if a user continues the gestureacross the second gesture capture region 124, the window 1420, shown onthe touch sensitive display 110, may expand to fill both the touchsensitive display 110 and the second touch sensitive display 114, shownin diagrams 1424 through 1432. Thus, the change of display can be anexpansion of a window over the first and second touch sensitive displayaa0, 114. In this way, the gesture capture regions 120, 124 andoff-screen gesture area 1232 provide for a method of managing windowsand provides different functionality or added functionality to thatwhich may be accomplished in the touch sensitive displays 110 and 114.

An embodiment of a method 1500 for executing an application is shown inFIG. 15. While a general order for the steps of the method 1500 is shownin FIG. 15. Generally, the method 1500 starts with a start operation1504 and ends with an end operation 1520. The method 1500 can includemore or fewer steps or can arrange the order of the steps differentlythan those shown in FIG. 15. The method 1500 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method1500 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-14.

Method 1500 can also start with a device 100 having a touch sensitivedisplay 110 and second touch sensitive display 114 (also referred to asscreens). The device 100 can include a seam between the first and secondtouch sensitive displays 110, 114, as evident in FIGS. 1A through 1J.The device 100 can receive a first user input into a touch sensitivedisplay 110, in step 1508. The user may then receive a second user inputin a second touch sensitive display 114, in step 1512. Based on one ormore factors, the device 100 can associated or interrelate the first andsecond user interface inputs, in step 1516. The interrelation of thefirst and second interface inputs may be to provide certain displayinteractions on the device 100 that occur across the seam of thedisplay. Examples of these interactions may be as explained inconjunction with FIGS. 16 through 18.

To interrelate the first user input and the second user input, thedevice 100 may determine if the two inputs are within temporal proximityto each other. In other words, the device 100 may determine if thesecond user input occurs at some predetermined time after the first userinterface input. This predetermined amount of time may be millisecondsor microseconds. There may be a longer period of time that the device100 waits to determine if the inputs are within temporal proximity.Regardless, if the second user input happens before the predeterminedamount of time, the device 100 can determine that the first user inputand second user input are within temporal proximity and should beinterrelated.

If the two inputs are within temporal proximity, then the device 100 candetermine that the first user input and second user interface input arepart of a single user interaction with the device 100. A single userinteraction can occur across the seam, and thus, while the interactionis one single interaction to a user, it will appear as a first input ina touch sensitive display 110 and a second input into a second touchsensitive display 114 for the device 100. The single user interactioncan begin on a touch sensitive display 110 and end on a second touchsensitive display 114 or vice versa.

An example of a user interaction across the seam is shown in FIG. 16through 17. As shown in FIG. 16, the environment 1600 for the device 100shows a first window 1604 on a touch sensitive display 110. A secondwindow 1608 is currently displayed on the second touch sensitive display114.

Referring now to FIG. 17, the device 100 can receive a user interfaceinput. In the environment 1700 the user may receive or may conduct adrag gesture 400 that starts on the touch sensitive display 110 andinteracts with window 1604. As the user begins to drag the window 1604to the right onto the second touch sensitive display 114, the window1604 begins to move and is shown in environment 1700 as being displayedon both the touch sensitive display 110 and the second touch sensitivedisplay 114. While the gesture begins on the touch sensitive display 110at point 1704, the gesture crosses the seam at area 1712 and thencontinues and ends at point 1708.

To the device 100, there is a first user interface input 1716 and asecond user interface input 1720 that occur on the touch sensitivedisplay 110 and the second touch sensitive display 114, respectively. Ifthe user interface input or single user interaction ends on the secondtouch sensitive display 114, as shown in FIG. 17, the display may bechanged as shown in FIG. 18. Here, in the environment 1800, the desktopas 1804 is now shown on the touch sensitive display 110 and the window1604 is now shown on the second touch sensitive display 114. Thus, theuser has conducted a drag and drop of the window 1604 from the touchsensitive display 110 to the second touch sensitive display 114.

If the single user interaction does not occur as that shown in FIG. 17but rather the portion 1720 of the interface input, which should happenon the second user interface 114, is not within temporal proximity orthe user fails to move their finger across the seam of the display, thewindow 1604 may be dropped back onto the touch sensitive display 110, asthat shown in FIG. 16. However, if the interaction does occur as thatshown in FIG. 17, the window may be dragged and dropped across the seamof the display.

While doing the single user interaction, the finger of the user movesthe window across the seam and may not be in physical contact witheither the first or second touch sensitive displays 110, 114. The twouser interface inputs can overlap, such that the first user interfaceinput 1716 ends at some time after the second user interface input 1720begins on the second touch sensitive display 114.

An embodiment of a method 1900 for executing an application is shown inFIG. 19. While a general order for the steps of the method 1900 is shownin FIG. 19. Generally, the method 1900 starts with a start operation1904 and ends with an end operation 1940. The method 1900 can includemore or fewer steps or can arrange the order of the steps differentlythan those shown in FIG. 19. The method 1900 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method1900 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-18.

The method 1900 begins by providing a device 100 having a touchsensitive display 110 and a second touch sensitive display 114. Themethod 1900 provides a way of determining how a first user interfaceinput and a second user interface input, which occur across a seam, maybe interrelated. Here, the device 100 can receive a first user interfaceinput into a touch sensitive display 110, in step 1908. The device 100may determine a vector for the first user interface input, in step 1912.The vector can include a speed of the user interface input movement anda direction of the user interface input.

Based on the vector for the first user interface input, the device 100can predict that the first user interface input will continue across theseam of display onto a second user interface 114 in an amount of time,in step 1916. In this way, the device 100 can predict that the firstuser interface input will continue, at some time thereinafter, on thesecond touch sensitive display 114. However, it is possible that theuser interface input may stop before the user interface input crossesover a seam of the display. Thus, the device 100 predicts that the firstuser interface input will cross the seam of the display but verifiesthis prediction.

The device 100 can wait the amount of time, in step 1920. The amount oftime may be measured in microseconds, milliseconds, or some short amountof time in relation to the speed of the user interface input.Thereinafter, the device 100 can receive a second user interface inputin the second touch sensitive display 114, in step 1924. The device 100may then determine if the second user interface input was receivedwithin the amount of time predicted in step 1916, in step 1928. If thesecond user interface input is received within the amount of time, thedevice 100 can determine if the second user interface input and thefirst user interface input are part of a single user interaction. Thus,method 1900 may proceed YES to step 1932 with a determination that thetwo inputs were part of a single user interaction. However, if the twouser interface inputs are not received in the amount of time, then themethod 1900 proceeds NO to step 1940 where the device 100 may determinethat the two user interface inputs are not part of a single interaction,in step 1936.

The amount of time used to wait between the second user interface inputand the first user interface input may be predetermined. Thus, theamount of time may be set upon the coding of the operating system orsoftware within the device 100. Alternatively, the user may set theamount of time manually. Also, the amount of time used to wait for thesecond user interface may be calculated based on the vector. In thisway, the speed of the user interface input may be used to determine howsoon a second user interface input should be received on a second userinterface. The faster the movement the less time the device 100 may waitfor the second user interface input.

Furthermore, while the exemplary aspects, embodiments, and/orconfigurations illustrated herein show the various components of thesystem collocated, certain components of the system can be locatedremotely, at distant portions of a distributed network, such as a LANand/or the Internet, or within a dedicated system. Thus, it should beappreciated, that the components of the system can be combined in to oneor more devices, such as a tablet-like device, or collocated on aparticular node of a distributed network, such as an analog and/ordigital telecommunications network, a packet-switch network, or acircuit-switched network. It will be appreciated from the precedingdescription, and for reasons of computational efficiency, that thecomponents of the system can be arranged at any location within adistributed network of components without affecting the operation of thesystem. For example, the various components can be located in a switchsuch as a PBX and media server, gateway, in one or more communicationsdevices, at one or more users' premises, or some combination thereof.Similarly, one or more functional portions of the system could bedistributed between a telecommunications device(s) and an associatedcomputing device.

Furthermore, it should be appreciated that the various links connectingthe elements can be wired or wireless links, or any combination thereof,or any other known or later developed element(s) that is capable ofsupplying and/or communicating data to and from the connected elements.These wired or wireless links can also be secure links and may becapable of communicating encrypted information. Transmission media usedas links, for example, can be any suitable carrier for electricalsignals, including coaxial cables, copper wire and fiber optics, and maytake the form of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

Also, while the flowcharts have been discussed and illustrated inrelation to a particular sequence of events, it should be appreciatedthat changes, additions, and omissions to this sequence can occurwithout materially affecting the operation of the disclosed embodiments,configuration, and aspects.

In yet another embodiment, the systems and methods of this disclosurecan be implemented in conjunction with a special purpose computer, aprogrammed microprocessor or microcontroller and peripheral integratedcircuit element(s), an ASIC or other integrated circuit, a digitalsignal processor, a hard-wired electronic or logic circuit such asdiscrete element circuit, a programmable logic device or gate array suchas PLD, PLA, FPGA, PAL, special purpose computer, any comparable means,or the like. In general, any device(s) or means capable of implementingthe methodology illustrated herein can be used to implement the variousaspects of this disclosure. Exemplary hardware that can be used for thedisclosed embodiments, configurations and aspects includes computers,handheld devices, telephones (e.g., cellular, Internet enabled, digital,analog, hybrids, and others), and other hardware known in the art. Someof these devices include processors (e.g., a single or multiplemicroprocessors), memory, nonvolatile storage, input devices, and outputdevices. Furthermore, alternative software implementations including,but not limited to, distributed processing or component/objectdistributed processing, parallel processing, or virtual machineprocessing can also be constructed to implement the methods describedherein.

In yet another embodiment, the disclosed methods may be readilyimplemented in conjunction with software using object or object-orientedsoftware development environments that provide portable source code thatcan be used on a variety of computer or workstation platforms.Alternatively, the disclosed system may be implemented partially orfully in hardware using standard logic circuits or VLSI design. Whethersoftware or hardware is used to implement the systems in accordance withthis disclosure is dependent on the speed and/or efficiency requirementsof the system, the particular function, and the particular software orhardware systems or microprocessor or microcomputer systems beingutilized.

In yet another embodiment, the disclosed methods may be partiallyimplemented in software that can be stored on a storage medium, executedon programmed general-purpose computer with the cooperation of acontroller and memory, a special purpose computer, a microprocessor, orthe like. In these instances, the systems and methods of this disclosurecan be implemented as program embedded on personal computer such as anapplet, JAVA® or CGI script, as a resource residing on a server orcomputer workstation, as a routine embedded in a dedicated measurementsystem, system component, or the like. The system can also beimplemented by physically incorporating the system and/or method into asoftware and/or hardware system.

Although the present disclosure describes components and functionsimplemented in the aspects, embodiments, and/or configurations withreference to particular standards and protocols, the aspects,embodiments, and/or configurations are not limited to such standards andprotocols. Other similar standards and protocols not mentioned hereinare in existence and are considered to be included in the presentdisclosure. Moreover, the standards and protocols mentioned herein andother similar standards and protocols not mentioned herein areperiodically superseded by faster or more effective equivalents havingessentially the same functions. Such replacement standards and protocolshaving the same functions are considered equivalents included in thepresent disclosure.

The present disclosure, in various aspects, embodiments, and/orconfigurations, includes components, methods, processes, systems and/orapparatus substantially as depicted and described herein, includingvarious aspects, embodiments, configurations embodiments,subcombinations, and/or subsets thereof. Those of skill in the art willunderstand how to make and use the disclosed aspects, embodiments,and/or configurations after understanding the present disclosure. Thepresent disclosure, in various aspects, embodiments, and/orconfigurations, includes providing devices and processes in the absenceof items not depicted and/or described herein or in various aspects,embodiments, and/or configurations hereof, including in the absence ofsuch items as may have been used in previous devices or processes, e.g.,for improving performance, achieving ease and\or reducing cost ofimplementation.

The foregoing discussion has been presented for purposes of illustrationand description. The foregoing is not intended to limit the disclosureto the form or forms disclosed herein. In the foregoing DetailedDescription for example, various features of the disclosure are groupedtogether in one or more aspects, embodiments, and/or configurations forthe purpose of streamlining the disclosure. The features of the aspects,embodiments, and/or configurations of the disclosure may be combined inalternate aspects, embodiments, and/or configurations other than thosediscussed above. This method of disclosure is not to be interpreted asreflecting an intention that the claims require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive aspects lie in less than all features of a singleforegoing disclosed aspect, embodiment, and/or configuration. Thus, thefollowing claims are hereby incorporated into this Detailed Description,with each claim standing on its own as a separate preferred embodimentof the disclosure.

Moreover, though the description has included description of one or moreaspects, embodiments, and/or configurations and certain variations andmodifications, other variations, combinations, and modifications arewithin the scope of the disclosure, e.g., as may be within the skill andknowledge of those in the art, after understanding the presentdisclosure. It is intended to obtain rights which include alternativeaspects, embodiments, and/or configurations to the extent permitted,including alternate, interchangeable and/or equivalent structures,functions, ranges or steps to those claimed, whether or not suchalternate, interchangeable and/or equivalent structures, functions,ranges or steps are disclosed herein, and without intending to publiclydedicate any patentable subject matter.

What is claimed is:
 1. A method, comprising: providing a device havingat least a first screen with a first display, a second screen with asecond display, and a seam between the first and second screens;displaying a first desktop on the first display; opening a firstapplication; ceasing display of the first desktop on the first display;displaying a first window of the first application on the first display,wherein the first window is active; opening a second application;displaying a second window of the second application on the seconddisplay, wherein the second window is active; receiving a first userinterface input in the first screen; determining a vector for the firstuser interface input; predicting, using the vector, that the first userinterface input will continue onto the second screen; waiting an amountof time for a second user interface input to be received in the secondscreen; receiving the second user interface input in the second screen,wherein the first user interface is in temporal proximity to the seconduser interface input; determining, when the second user interface inputis received within the amount of time, that the first user interfaceinput and the second user interface input are part of a single userinteraction with the device, wherein the single user interaction isacross the seam of the device; and interrelating the first and seconduser inputs, wherein determining the vector for the first user interfaceinput further comprises: determining a speed of the first user interfaceinput; and determining a direction of the first user interface input,wherein the amount of time is based on the determined vector.
 2. Themethod claim 1, screen further comprising: moving the first window tothe second display; ceasing display of the second window on the seconddisplay, wherein the second window is inactive; displaying the firstdesktop on the first display; and displaying the first window on thesecond display.
 3. The method of claim 2, wherein the single userinteraction is a drag of the first window.
 4. The method of claim 2,wherein moving the first window to the second display further comprises:moving the first window in a direction of the vector toward the seconddisplay, wherein during the moving the first window is displayed atleast partially on each of the first display and the second display;during the moving, uncovering the first desktop on the first display asthe first window moves onto the second display; and during the moving,covering the second window with the first window as the first windowmoves onto the second display.
 5. The method of claim 1, furthercomprising: determining, when the second user interface input is notreceived within the amount of time, that the first user interface inputand the second user interface input are not part of the single userinteraction with the device; and dropping the first window on the firstdisplay.
 6. The method of claim 5, first screen further comprising:before determining that the first user interface input and the seconduser interface input are not part of the single user interaction withthe device, moving the first window in a direction of the vector towardthe second display, wherein during the moving the first window isdisplayed at least partially on each of the first display and the seconddisplay, wherein the first desktop is at least partially displayed onthe first display, and wherein the second window is at least partiallycovered by the first window on the second display; and after determiningthat the first user interface input and the second user interface inputare not part of the single user interaction with the device, moving thefirst window back to the first display, wherein the first desktop is notdisplayed, and wherein the second window is displayed.
 7. The method ofclaim 1 , wherein, for at least a portion of the single userinteraction, a finger of the user crosses the seam and is not inphysical contact with either a first display or the second display.
 8. Adevice, comprising: a first screen with a first display; a second screenwith a second display; an off screen gesture area; a memory; a processorin communication with the memory, the first screen, and the secondscreen, the processor operable to: display a first desktop on the firstdisplay; open a first application; cease display of the first desktop onthe first display; display a first window of the first application onthe first display, wherein the first window is active; open a secondapplication; display a second window of the second application on thesecond display, wherein the second window is active; receive a firstuser interface input in the first screen; determine a vector for thefirst user interface input; predict, using the vector, that the firstuser interface input will continue onto the second screen; wait anamount of time for the second user interface input to be received in thesecond screen; receive the second user interface input in the secondscreen, wherein the first user interface input is in temporal proximityto the second user interface input; determining, when the second userinterface input is received within the amount of time, that the firstuser interface input and the second user interface input are part of asingle user interaction with the device, wherein the single userinteraction is across the seam of the device; and interrelate the firstand second user inputs; wherein determining the vector for the firstuser interface input further comprises the operations: determining aspeed of the first user interface input; and determining a direction ofthe first user interface input, wherein the amount of time is based onthe determined vector.
 9. The device of claim 8, wherein the first userinterface input is in temporal proximity to the second user interfaceinput, wherein if the second user interface input is not within temporalproximity of the first user interface input, the first window is droppedon the display.
 10. The device of claim 8, wherein the processor isfurther operable to determine, when the second user interface input isreceived within the amount of time, that the first user interface inputand the second user interface input are part of a single userinteraction with the device.
 11. The device of claim 10, wherein thesingle user interaction is a drag of the first window, wherein the firstwindow is selected on the first screen, and wherein the processor isfurther operable to: before determining that the first user interfaceinput and the second user interface input are part of the single userinteraction with the device, move the first window in a direction of thevector toward the second display, wherein during the moving the firstwindow is displayed at least partially on each of the first display andthe second display, wherein the first desktop is at least partiallydisplayed on the first display, and wherein the second window is atleast partially covered by the first window on the second display; afterdetermining that the first user interface input and the second userinterface input are part of a single user interaction with the device,move the first window to the second display, wherein the processorceases display of the second window on the second display, wherein thesecond window is inactive, wherein the first desktop is displayed on thefirst display, and wherein first window is displayed on the seconddisplay; and after determining, when the second user interface input isnot received within the amount of time, that the first user interfaceinput and the second user interface input are not part of a single userinteraction with the device, move the first window back to the firstdisplay, wherein the first desktop is not displayed on the firstdisplay, and wherein the second window is displayed on the seconddisplay.
 12. The device of claim 11, wherein, for at least a portion ofthe single user interaction, a finger of the user crosses a seam betweenthe first and second screens and is not in physical contact with eitherthe first or second display and wherein determining the vector for thefirst user interface input further comprises the processor: determininga speed of the first user interface input; and determining a directionof the first user interface input.
 13. A non-transitory computerreadable medium having stored thereon computer-executable instructions,the computer executable instructions causing a processor of a device toexecute a method for providing a user interface, the computer-executableinstructions comprising: instructions to display a first desktop on afirst display of a first screen of the device; instructions to open afirst application; instructions to cease display of the first desktop onthe first display; instructions to display a first window of the firstapplication on the first display, wherein the first window is active;instructions to open a second application; instructions to display asecond window of the second application on a second display of a secondscreen of the device, wherein the second window is active; instructionsto receive a first user interface input in the first screen;instructions to determine a vector for the first user interface input;instructions to predict, using the vector, that the first user interfaceinput will continue onto the second screen; instructions to wait anamount of time for the second user interface input to be received in thesecond screen; instructions to receive the second user interface inputin the second screen, wherein the first user interface input is intemporal proximity to the second user interface input; instructions todetermine, when the second user interface input is received within theamount of time, that the first user interface input and the second userinterface input are part of a single user interaction with the device,wherein the single user interaction is across the seam of the device;and instructions to interrelate the first and second user inputs;wherein the instructions to determine the vector for the first userinterface input further comprises instructions to: determine a speed ofthe first user interface input; and determine a direction of the firstuser interface input, wherein the amount of time is based on thedetermined vector.
 14. The non-transitory computer readable medium ofclaim 13, wherein the first user interface input is in temporalproximity to the second user interface input, wherein if the second userinterface input is not within temporal proximity of the first userinterface input, the first window is dropped on the display, and whereinthe instructions to determine the vector for the first user interfaceinput further comprise instructions to determine a speed of the firstuser interface input and instructions to determine a direction of thefirst user interface input.
 15. The non-transitory computer readablemedium of claim 13, further comprising instructions to determine, whenthe second user interface input is received within the amount of time,that the first user interface input and the second user interface inputare part of a single user interaction with the device.
 16. Thenon-transitory computer readable medium of claim 15, wherein the singleuser interaction is a drag of the first window, and wherein theinstructions further comprise: instructions to move, before determiningthat the first user interface input and the second user interface inputare part of the single user interaction with the device, the firstwindow in a direction of the vector toward the second display, whereinduring the moving the first window is displayed at least partially oneach of the first display and the second display, wherein the firstdesktop is at least partially displayed on the first display, andwherein the second window is at least partially covered by the firstwindow on the second display; instructions to move, after determiningthat the first user interface input and the second user interface inputare part of a single user interaction with the device, the first windowto the second display, wherein the processor ceases display of thesecond window on the second display, wherein the second window isinactive, wherein the first desktop is displayed on the first display,and wherein first window is displayed on the second display; andinstructions to move, after determining, when the second user interfaceinput is not received within the amount of time, that the first userinterface input and the second user interface input are not part of asingle user interaction with the device, the first window back to thefirst display, wherein the first desktop is not displayed on the firstdisplay, and wherein the second window is displayed on the seconddisplay.
 17. The non-transitory computer readable medium of claim 15,wherein, for at least a portion of the single user interaction, a fingerof the user crosses the seam and is not in physical contact with eithera first or second touch sensitive display.